Linked by Stefan Michalowski, M. Sc. on Thu 19th Aug 2004 08:27 UTC
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Lot's of OSS projects take care not to break backwards binary-compatibility: glibc, KDE, gnome, qt, gtk+, etc.
GCC keeps breaking C++ compatibility, and with good reason. I'd rather not have to live with ABI bugs just so some stupid closed-source program I don't even use can keep working. In contrast, Visual C++'s hell-bent desire to keep backwards compatibility have hurt it. GCC 3.x uses a cool table-based exception-handling mechanism that has no runtime cost. Meanwhile, Visual C++, to preserve compatibility, can't use this sort of mechanism, and uses Windows' structured exception handling, which entails a performance hit.