--- Begin Message ---
* Alan W. Irwin <[EMAIL PROTECTED]> [2008-09-04 16:17]:
> According to that wiki, the advantages of limiting symbols that are exported
> is smaller libraries and less loading latency.
One important additional advantage is that you do not expose users to the
internal symbols, otherwise they could be tempted to use them, which are
outside the public API.
> I would love to see that happen so I agree with Rafael this is well worth
> doing. However, an alternative implementation would be to follow the
> cookbook in the above wiki to extend what we currently do for windows in
> include/pldll.h to handle the gcc case. The obvious advantage of this
> approach is once include/pldll.h is changed it affects both current API and
> future API so there is some benefit in terms of not having to maintain an
> additional file such as included in Rafael's patch whenever we add to our
> API.
The separated file containing a list of symbols seems to be the simplest
approach, but there are others too. See
http://developer.apple.com/documentation/DeveloperTools/Conceptual/DynamicLibraries/Articles/DynamicLibraryDesignGuidelines.html
--
Rafael
--- End Message ---
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel
