rene.eberhard> It't also easy to use C++ objects in a C code.
Oh? How so? Is that portable?
rene.eberhard> The problem is that a C++ .lib compiled with Borland
rene.eberhard> can not be used with the MS VC++ compiler and vice
rene.eberhard> versa. I assume the same is true for Unix compiles.
Your assumption is correct.
rene.eberhard> It is not standardized how objects are put into a .lib.
Not quite. The unstandardised part is how function and method
argument type info is saved in the object file (this is needed to make
functions overloadable). Most compilers do it with "name mangling",
meaning they add cryptic info strings to the function name, thus
describing the types of all the arguments. The actual syntax of those
strings are highly compiler-dependent...
--
Richard Levitte \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken \ S-161 43 BROMMA \ T: +46-8-26 52 47
\ SWEDEN \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
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]
