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.
In the GCC STL lib, std::string.clear() only resets pointers and keeps
the allocated memory while std::string.erase() deletes the allocated space.
People wo develop with GCC rely on this fact and having two different STL libs
could be a bit difficult.....
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
opensolaris-discuss mailing list
[email protected]
