User: Password:
|
|
Subscribe / Log in / New account

C++ incompatibility history

C++ incompatibility history

Posted Mar 28, 2008 0:12 UTC (Fri) by giraffedata (subscriber, #1954)
In reply to: C++ incompatibility history by jreiser
Parent article: Striking gold in binutils

It's also important to note that the echoes of those historical compatibility problems can be with us for a long time. I try to use C++, but it's a trial, because I have systems that have roots going back to Gcc 2 days. There is no switch on these systems I can flip to recompile every program and library with a current compiler. A C++ program compiled with Gcc 3 will not work with an existing C++ library, and vice versa. So when I write new C++ code, I compile with Gcc 2, and probably always will.

I recently learned, painfully, that current 'ld' has a similar compatibility problem -- something to do with throwing an exception across object modules.

It's worth noting that none of these problems exist with C. I.e. the zero-headache alternative for me is to use C.


(Log in to post comments)

C++ incompatibility history

Posted Mar 28, 2008 3:49 UTC (Fri) by pflugstad (subscriber, #224) [Link]

Heh - I'm still forced to use a EGCS 1.1 cross compiler for a certain embedded OS I work with.
Talk about painful.  Even more so: it's running under an _old_ version of cygwin on windows
(and if you know much about cygwin, you know the old versions had lots of interesting bugs and
multiple versions on the same system don't play nice together, so it ends up trashing the more
modern cygwin installs)... sigh...

Sorry, just had to whine...


Copyright © 2018, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds