generic way to access C++ libs?

[Jorgen Grahn]

On Tue, 09 Nov 2004 10:24:01 GMT, Neil Hodgson <nhodgson at bigpond.net.au> wrote:
> Gabriel Zachmann:
>> >     The layout is also modified by various compiler options.
>>
>> really? that would mean that c++ libs themselves are
>> not binary compatible among each other?
> 
>    I was thinking in terms of Microsoft C++ options like the vtordisp
> setting used to handle virtual inheritance (/vd0 or /vd1), pointer to member
> representation (/vm*), and the old favourite struct alignment (/Zp*).
> Borland adds options for allowing small enumerations to take only one byte
> (-b-), zero size empty base classes (-Ve), zero size empty members (-Vx),
> and a layout compatible with old compiler versions (-Vl).
> 
>    Much of the time C++ code only has to be compatible with the other
> modules it is delivered with.

But most of the time it has to be compatible with the standard library.

Even if these flags exist, I think it's very rare to encounter more than one
layout, for one specific compiler/compiler version/architecture.

/Jorgen

-- 
  // Jorgen Grahn <jgrahn@       Ph'nglui mglw'nafh Cthulhu
\X/                algonet.se>   R'lyeh wgah'nagl fhtagn!