Linked by Thom Holwerda on Mon 25th Jun 2007 20:30 UTC, submitted by Nitsudima
"The Free Software community is well known for its diversity. This is most obvious at the application level, but even exists in the context of operating systems. David Chisnall takes a break from UNIX-derivatives and explores some of the more esoteric options." Note: From experience, I can say that the author's claim that "Haiku is more or less ready for their 1.0 release in terms of features" is a bit overambitious.
Thread beginning with comment 250662
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: UNIX-likes boring?
by Vanders on Tue 26th Jun 2007 14:07
in reply to "RE: UNIX-likes boring?"
Member since:2005-07-06
RE[3]: UNIX-likes boring?
by Mike Pavone on Tue 26th Jun 2007 20:36
in reply to "RE[2]: UNIX-likes boring?"
Member since:2006-06-26
The ABI was changed to comply with the cross-vendor C++ ABI. It wasn't like the GCC guys sat down one day and said "Hey you know what, let's change the C++ ABI for the hell of it. That'll really annoy everyone!"
Well technically GCC 3.X and later use the name mangling scheme dictated by the IA64 ABI. It's hardly a standard on other processor architectures (though from what I gather, Intel's C++ compiler uses it for x86 as well, but this is unsurprising since Intel is responsible for the IA64 ABI).
See http://en.wikipedia.org/wiki/Name_mangling#How_different_compilers_...
You would think they would have left an option for the old way, but perhaps they made other ABI changes (like the way exceptions are handled) that would have made having a proper backwards compatability option practical.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-08-09
Haiku still uses an early GCC 2x release to avoid breaking compatibility with BeOS R5
Problems caused by GCC guys, because they changed the virtual call interface
and name mangling in version 3. In version 4 compatibility was broken again, at least for Sparc.
So, for people from real world, they made impossible to upgrade.