[EMAIL PROTECTED] (Ulf M�ller):
>>> without any problems with newly compiled shared libraries: The new
>>> library functions will expect one parameter that is not actually there
>>> and will take whatever happens to be on the stack and pass it to the
>> Although you are likely to get away with this, it isn't strictly legal.
> Doesn't work for Windows DLLs, does it?
Why not? At least those built with Mingw32 use the "cdecl" calling
convention, i.e. show the usual behaviour for C programs where the
caller and the callee operate pretty much independently (i.e. the
callee does not take anything from the stack, it justs looks at it);
if this is different with other C compilers, then we don't even have
intra-version binary compatibilty between compilers. crypto/cryptlib.c
declares DLLEntryPoint as WINAPI, which presumably requests a calling
convention different from the one usually employed for C programs.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
