On Mon, Sep 08, 2008 at 02:20:48PM -0700, Steve Clamage wrote:
> The feature would not be available on Solaris 9 or earlier. We have 
> precedent for such a limitation: full C99 conformance is similarly not 
> available. But I don't think restricting the availability to 
> SNV/OpenSolaris is acceptable. Currently, full Sun support (e.g. for 

Why not?  Plenty of things are in Solaris Nevada / OpenSolaris that will
not be backported to Solaris 10.  Whether to backport is a business
issue, not an ARC issue.

> [...]
> 
> It might be possible to deliver a single version of the runtime library 
> (per platform) compiled with -mt to be used by both MT and non-MT 
> programs, but it would have performance implications for single-threaded 
> programs. We think a better solution would be to have two libraries, to 
> ensure no conflict between MT and non-MT code, and to eliminate 
> gratuitous performance loss in single-threaded code. (In MT code, the 
> library must lock critical regions of an object during manipulation by 
> library functions.)

Solaris 10 and up have a unified process model.  Why should C++ on
Solaris not have a unified process model too?

Nico
-- 

Reply via email to