Symbian3/SDK/Source/GUID-9F22E663-8BC4-5502-879F-E6B790465E74.dita
changeset 0 89d6a7a84779
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/Symbian3/SDK/Source/GUID-9F22E663-8BC4-5502-879F-E6B790465E74.dita	Thu Jan 21 18:18:20 2010 +0000
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
+<!-- This component and the accompanying materials are made available under the terms of the License 
+"Eclipse Public License v1.0" which accompanies this distribution, 
+and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
+<!-- Initial Contributors:
+    Nokia Corporation - initial contribution.
+Contributors: 
+-->
+<!DOCTYPE concept
+  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<concept xml:lang="en" id="GUID-9F22E663-8BC4-5502-879F-E6B790465E74"><title>exportunfrozen</title><prolog><metadata><keywords/></metadata></prolog><conbody><p><codeph>exportunfrozen</codeph> </p> <p>Use the <codeph>exportunfrozen</codeph> statement if unfrozen exports are to appear in the project’s import library. </p> <p>When it is used, the import library is created as a side-effect of linking so that all exported functions, even unfrozen ones, appear in the import library. This also means that import libraries for compatible ABIs are not created. </p> <p>If this is not used, you must supply a <filepath>.def</filepath> file with the frozen exports. </p> <p>Use of <codeph>exportunfrozen</codeph> is only recommended for the early stages of project development, when the Application Programming Interface is likely to be subject to change.</p> </conbody></concept>
\ No newline at end of file