Joerg Schilling wrote: > Alan Coopersmith <alan.coopersmith at sun.com> wrote: > >> You may be remembering the discussions about why Sun chose GNOME/GTK over >> KDE/Qt - and for the primary development GUI toolkit, that was an issue, but >> for additional software that's provided as an option, or software that's >> being >> used like kdm, but not offered as a developement kit to build on, it >> shouldn't >> be an obstacle. (It was also much more of an issue when the GNOME vs. KDE >> decision was made 8 years ago at Sun, since the choice was between $3000 >> Sun C++ and $0 g++ - but now that Sun C++ is also free, the price is no >> longer a barrier to usage/adoption.) > > So you would propose to create SS compiled libraries and tell users to also > use > Sun Studio if they like to use the libs? OK, if the price/availability > was the main reason, this looks different now.
That, and the other technical aspect: any Sun customer who has developed in-house C++ libraries, and has built them with any version of Workshop/Forte/Studio supporting Version 5 of the Sun C++ ABI, will be able to link and use these in-house libraries, and have the expectation that they will Just Work(TM). I may run the risk of sounding like a broken record, but, in the world of C++ Compilers, maintaining C++ ABI compatibility across 7 different compiler releases is a rare, and remarkable technical feat. --Stefan -- Stefan Teleman Sun Microsystems, Inc. Stefan.Teleman at Sun.COM
