Follow-up question: Re: [lug] g++ question: dynamic casts?

Tom Tromey tromey at
Thu Jan 31 11:28:18 MST 2002

>>>>> "Tkil" == Tkil  <tkil at> writes:

Tkil> either way, it's a bit of a mess.  as Tom pointed out, however, there
Tkil> should be some light at the end of the tunnel, with the 3.0 and higher
Tkil> releases supporting a stable, standard, cross-platform ABI.

It's not as nice as you think :-(.  My understanding is that they've
defined libstdc++ as not being part of the ABI.  This means subsequent
releases of libstdc++ probably won't be binary compatible.  This makes
sense, but it also makes the C++ programmer's life difficult.

Choosing your toolchain depends hugely on what you're doing.  If
you're shipping free software, then you probably want to make sure it
works with various common compilers.  If you're shipping a binary
application, then use the compiler from your target platform (e.g.,
shipping on RH 7.2, then use gcc 2.96).  If you're shipping an
embedded application, pick the compiler that gives you what you want
(best performance, smallest size, whatever).  There's not really a
canned answer.


More information about the LUG mailing list