Richard Levitte - VMS Whacker wrote:
>
> 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.
>
An external DLL might use DECLARE_ASN1_FUNCTIONS() in its header file
and then drag in OPENSSL_EXTERN if it was added to the macro.
OPENSSL_EXTERN would then need that behaviour to work.
If OPENSSL_EXTERN is considered illegal in external applications they
need some other way to achieve the same end.
Steve.
--
Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/
Personal Email: [EMAIL PROTECTED]
Senior crypto engineer, Celo Communications: http://www.celocom.com/
Core developer of the OpenSSL project: http://www.openssl.org/
Business Email: [EMAIL PROTECTED] PGP key: via homepage.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
