Why does this now work?

[Eljay Love-Jensen]

Hi Graeme,

If the libraries are C libraries, the C ABI is well defined.  I'm surprised 
that GCC 2.95 would have issues.

If the libraries are C++ libraries -- have and propagate exceptions, don't 
use extern "C", rely on Sun's C++ ABI (which is non-standard, as there 
ISN'T a C++ ABI standard at the moment) -- then I'd be surprised if you 
could get the Sun C++ object code to link with GCC C++ object code even in 
trivial C++ examples.

Are these libraries 1) a .so and .h files (dynamic linkage), or 2) a .a and 
.h files (static linkage), or are they 3) source code that you compile 
yourself?

If #3, then I'm somewhat surprised that they DIDN'T work with GCC 
2.95.  Although, GCC 2.95 was close to compliance with the 1995-1996 C++ 
draft spec (a moving target), and GCC 3.2 is very close (if not dead on) to 
the C++ ISO/IEC 14882:1998 spec.

Wasn't the GCC quote, "As close to the ISO/IEC 14882:1998 spec as possible, 
and no closer"...?  *grin*

Anyone implement "export" yet?  Other than Comeau C++, I presume.

--Eljay