From: Dr S N Henson <[EMAIL PROTECTED]>
drh> What I'm not sure about is how this can work with an application that
drh> wants to compile an additional external DLL which might effectively need
drh> OPENSSL_EXTERN (via DECLARE_...) to mean two different things in
drh> different places. That is import for stuff defined in the OpenSSL header
drh> files and export for stuff it defines itself in its own header files
drh> when its compiled or import everywhere when its being linked to.
Why should an external application use OPENSSL_EXTERN for it's own
DLL's? Or why should an external DLL use OPENSSL_EXTERN for it's own
purposes? I see such use as a flaw in that applications or DLL.
OPENSSL_EXTERN should be used for OpenSSL stuff and nothing else.
It's up to the author(s) of that application or DLL to create theirv
own EXTERN macros as they see fit. Period.
--
Richard Levitte \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
Redakteur@Stacken \ SWEDEN \ or +46-709-50 36 10
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, Celo Communications: http://www.celocom.com/
Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
