Linked by Eugenia Loli-Queru on Wed 26th Dec 2007 09:50 UTC
There is a controversy in the Linux world. It doesn't have to do with Microsoft, or anything overtly technical. It may seem, to the outsider, the open source equivalent of the question, "Boxers or briefs?" But it's much more serious than that. More here.
Thread beginning with comment 293207
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[3]: KDE not stable API?
by kaiwai on Wed 26th Dec 2007 15:21
in reply to "RE[2]: KDE not stable API?"
Member since:2005-07-06
Regarding the C++ reliability - it'll be interesting once LLVM's CLANG front end is finished; with the backed support of Apple it'll mean that ABI stability will be a must - hopefully then for C++ ABI stability, the competition another compiler brings, it'll force GNU to get its act together.
At the end of the day, if harmony can be found between them, then hopefully LLVM will be mature enough for GCC to be yanked from Solaris and replaced with an opensource compiler which realises playing nice with each other (including proprietary compilers) is a good thing(tm).
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-06
The C++ ABI is not standard and it is far from be stable (including between two versions of the same C++ compiler), so, creating some library with SUNWpro C++ compiler will not be useful for an application written with g++. This is a very critical problem because KDE is written in C++;
The main problem with C++ ABI is the GNU folks. They keep changing their C++ ABI. Sun has had a very stable C++ ABI for years now. This creates the gross incompatibility situation discussed here.
This part isn't true. Trolltech supports Sun Studio (SUNWPro C++ compiler) fully on Solaris.
Adopting gcc over Sun Studio isn't an option as the gnu folks refuse to integrate certain patches that would fix many of the performance problems that some of their generated code has on SPARC, etc.
Yes, this is another reason.
3. Solaris has invested a lot of resources in the GNOME accessibility framework, so, GNOME fully implements an accessibility standard [I do not remember its code] and KDE, no.
This is one truth. GNOME has a far more mature accessibility environment and Sun, as a public US company, has a necessary commitment to section 508 compliance.