> >> While we prefer to use the Studio C compiler, we have been allowing gcc > >> to be used for components in SFW requiring modifications to avoid gcc > >> "features" that aren't available in Studio. We haven't been allowing > >> the use of g++ for interface compatibility and stability reasons. > > > > Ah, now I see the urgency for Apache c++ STL library. Thanks for the > > explanation. > > > FWIW, I suspect that you may be missing a couple of key issues still. > > * You don't appear to be able to link Studio CC compiled objects > with g++ compiled objects. > At a very simple level, they appear to do name mangling > differently, but I am told that there are other issues as well. > * Compatibility issues pop up between g++ versions and they don't > guarantee backward compatibility with objects built using older > versions of g++ (or so I am told).
Yup, I have been hating C++ long enough to know it's evil :) http://www.parashift.com/c++-faq-lite/big-picture.html#faq-6.15 Usually I have the feeling that my knowledge of particular programming language increases over time, but with C++ I have sort of reversed feeling :) Cheers -- Vlad -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 193 bytes Desc: not available URL: <http://mail.opensolaris.org/pipermail/sfwnv-discuss/attachments/20080922/aafb06ef/attachment.bin>
