|Symbols in library. email@example.com (2003-07-31)|
|Re: Symbols in library. v.Abazarov@attAbi.com (Victor Bazarov) (2003-08-04)|
|Re: Symbols in library. firstname.lastname@example.org (Artie Gold) (2003-08-04)|
|Re: Symbols in library. email@example.com (2003-08-10)|
|Re: Symbols in library. firstname.lastname@example.org (2003-08-20)|
|Re: Symbols in library. email@example.com (2003-08-23)|
|Re: Symbols in library. firstname.lastname@example.org (2003-08-23)|
|Re: Symbols in library. email@example.com (Dave Thompson) (2003-09-01)|
|Date:||23 Aug 2003 23:16:11 -0400|
|Organization:||AOL Bertelsmann Online GmbH & Co. KG http://www.germany.aol.com|
|Posted-Date:||23 Aug 2003 23:16:11 EDT|
firstname.lastname@example.org (Torbak) schreibt:
>I fact my question should be shortly discribe like this : Libraries
>are files wich contain compiled code. Then to be linked, they contain
>symboles description to discribe to the linker where it can find
>functions which are accesible in the library.
It's just the linker which also has to know about private/static functions, so
that these also can be linked into a program.
>I use microsoft C compiler.
If you really want the names of static functions to disappear, then make the
library a DLL. Then the linker can resolve all internal references when linking
the DLL, so that only the exported (non-static) names remain visible in the
exports section of the DLL.
Return to the
Search the comp.compilers archives again.