that is, tracking those that it has that [Open]Solaris currently doesn't,
and at least for those whose description appears to be unlikely to change,
implementing them, such that they're available ASAP once the final
revision to the spec comes out (this year, I think!)?  If there were such a 
list,
I'd like to think it wouldn't be too bad to get people to sign up to write them.

I also wonder whether anyone has done a similar comparision with the LSB,
not with a mind to necessarily adopting everything, but at least those that
present no incompatibilities with what's there now or with the Austin Group
draft, might be most commonly a problem porting C/C++ code to Solaris,
and otherwise aren't a problem-in-the-making.
 
 
This message posted from opensolaris.org
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code

Reply via email to