   to import or to export
  can somebody explain when an object/func is being said to be imported or exported?
  exported: made available to others.imported: made available by others.others can be programs (via dynamic libraries), translations units (during linking), etc, depending on the context   “Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.”    — Brian W. Kernighan (C programming language co-inventor);  the thing that''s not clear to me is why the need for dual import/export settings in projects?   ;  Dual import/export settings in projects? You lost me there. ;quote:Original post by vesoljc   the thing that's not clear to me is why the need for dual import/export settings in projects?    Header files are often written that way so that the very same header can be used both to build the library itself (where the macros expand to 'export' - the library makes its functions available to other programs) and when you *use* the library (where the macros expand to 'import' - the program uses the functions from the library).Basically, if IMPORT and EXPORT are the applicable attributes for your platform:foo.h#ifdef BUILDING_LIBRARY#define EXPORT_FLAG EXPORT#else#define EXPORT_FLAG IMPORT#endifEXPORT_FLAG int foo();   When you build   the library, do  #define BUILDING_LIBRARY, and include the header, which will cause foo() to be exported.When you use   the library, do not  #define BUILDING_LIBRARY, and include the header, which will cause foo() to be imported.   “Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.”    — Brian W. Kernighan (C programming language co-inventor) [edited by - Fruny on February 4, 2004 11:37:27 PM];  so, if using the standard exp file, this is not needed?   ;quote:Original post by vesoljc  so, if using the standard exp file, this is not needed?   Be careful with what you call "standard".   “Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.”    — Brian W. Kernighan (C programming language co-inventor);  true  