PSARC 2008/549 Re: Apache Standard C++ Library ARC Case

[John Plocher]

Looks like mucho lotso progress has been made.  It looks pretty good,
but I still have a couple of questions:

   o This case obsoletes STLport4 (section 4.1).  How will existing
     users of STLPort4 find out that we did this?  ("#warnings in
     headers...?)

   o This case starts libC on its own path towards Obsolescence (4.3, 4.4)
     Same comments apply as above, but not as urgently.

   o What are the actual dependencies between this project and the studio12
     compilers?

   o Who is signed up to track the Apache stdcxx project and update the
     bits in SFW over time, and how do you expect those bits to evolve?
     (picky interface taxonomy details needed, along with a bigger picture
     of who gets a chair when the music stops - erm, I mean, what happens
     when Apache comes out with incompatible change or does a Major 
     Version 5 or 6 ...)

and clarifications:

>> Stefan Teleman wrote:
>>     3.2.        The SFW Consolidation will provide pkg-config [ *.pc ]
>>     files for the Apache Standard C++ Library.  These files will encode
>>     the correct Sun Studio 12 command-line switches for:...

>>     3.3.        The SFW Consolidation will provide a default UNIX man
>>     page... will detail the mechanics of ...
>>     3.4.        The DevPro/Tools Group will provide integrated command-line
>>     support...
>>     3.5.	...  This document does not attempt to address the interfaces
>>     to be provided...

How can you create ".pc" files that encode the correct flags without
first knowing what the flags (interfaces) are?  See my dependency 
question above...

>> 4.	Future Directions, and Recommendations for Solaris Developers
...
>>     4.5.	The contents of this document do not establish ARC Precedent.

This conflicts with the statements in 4.1 thru 4.4 - of you expect any of them
to be followed, you *need* a precedent.

This is where I would like to see buy-in from the compiler team.

   -John