Garrett D'Amore wrote:
> Stefan Teleman wrote:
>>
>> New C++ code which must make use of Standard Language facilities not 
>> supported in libCstd.so.1, should use the Standard Compliant C++ 
>> Library (Apache) -- being proposed here, for the following reasons:
>>
>> - Fully Compliant with the 1998/2003 C++ Standard
>> - Full Internationalization and Localization support (absent in STLport4)
>> - Thread-safe
>> - 64-bit clean
>>
>> However: mixing any two different implementations of the Standard C++ 
>> Library in the same address space does not work.
> 
> So, if standards compliance is key, then lets have a *full* case 
> detailing the following:
> 
> 1) Marking libCrun and libCstd as Obsolete, and discourage their future 
> use.  (Possible EOF notices.)
> 2) Integration of Apache libstdc++.
> 3) Transition flags for compilers to select older C runtimes if required 
> for compatibility reasons.
> 4) Studio 13 (or somesuch) to use libstdc++ by default.
> 5) Full disclosure of g11n considerations for programs making use of 
> g11n features.  (How is locale-specific data managed?)
> 6) Full disclosure of any source incompatibilities between libraries.
> 7) Involvement from compiler folks (required for items #3 & #4)
> 8) Description of any expected future incompatibilities

These requirements are completely beyond the scope and intent of this ARC Case.

--Stefan

-- 
Stefan Teleman
Sun Microsystems, Inc.
Stefan.Teleman at Sun.COM


Reply via email to