Steve Clamage writes: > and he doesn't link to Solaris libraries that were written in C++. Do we > tell him, sorry, you can't use STLport on Open Solaris?
No, that'd be "removal." All that was asked for was "obsolescence." > Or should the > compiler emit a warning on every CC command saying STLport is obsolete? If it's not the right way to inform the user, then, no that's not what should be done. ARC requests always come with an implicit "don't just do whatever someone suggests; please use your head." The user should be informed in the most appropriate way possible that (a) the feature is obsolete [possibly going away in some unknown future release] and (b) there's a better replacement. > Do it in the Solaris documentation. I don't think the ARC has (or should have) much of a position on this part. The issue is delivering the appropriate documentation. How that's done is the project team's responsibility. Quibbling over compiler versus OS documentation on this list seems really out of scope to me. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
