Joerg Schilling wrote: >Ian Collins <[EMAIL PROTECTED]> wrote: > > > >>>What we can do for the problem? >>> >>>- Use as many pure C ABIs as possible >>> >>>- Create something like /usr/lib/gcc/ >>> to document the fact that the libraries inside are not compatible >>> with the Sun compiler C++ ABI >>> >>> >>> >>> >>> >>The Studio team are working on gcc ABI compatibility. With the source >>compatibility already in place, Studio CC may well end up as a drop in >>replacement for gcc. >> >> > >I am not sure whether this is so simple. > >There is STL which is just a different lib if you use gcc. > >In the Solaris STL lib, std::string.clear() and std::string.erase() >do the same: delete on the allocated space. > > > There isn't a "Solaris STL lib".
Sun Studio ships with the original Studio STL and stlport4. The original STL provides backwards compatibility, but I'd always recommend stlport for new code as it is closer to being fully standards compliant. The original STL (first shipped with CC5.0) never will be standards compliant, to make it so would involve changing the ABI used thus breaking backwards compatibility. Ian _______________________________________________ opensolaris-discuss mailing list [email protected]
