On Tue, Nov 08, 2005 at 06:04:05PM +0100, Andy Polyakov wrote: > extern "C" makes perfect sense, but PASCAL? It doesn't make sense... > Documentation references indicate that PASCAL capitalizes name [not to > mention alternative argument passing convention, but it's lesser problem > in this case, because we don't pass any arguments here], which means > that exported symbol should come out incompatible... So how come it > worked? But Borland apparently supports __cdecl, can you verify if it > does the trick?
I agree, the docs for BC++ indicate it should affect the name in other ways, but it did solve the issue of the GetProcAddress not finding the name.. Sadly I gave up experimenting after this since we couldn't get the thing to work reliably even given that, and eventually we coerced a build to happen with BC++6 which works all lovely and nice and everything "just happens". > But Microsoft C prepends the name with underscore... Well, it's then > stripped off by linker... I always get a bit dizzy in between Win32 > compilers... Ah, I think it's that that's the issue -- the BC++ linker doesn't (IIRC) strip off the underscore[1]. ISTR something involving adding them while doing VC++ -> BC++ library conversions. (It's been a while). [1] I miss UNIX's "nm" SO much while doing this stuff... ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
