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

[Stefan Teleman]

Hi.

My answers inline:

John Plocher wrote:
> 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...?)

Proposal:

- Compiler Error when passed -library=stlport4 switch, regardless of whether or 
not the header files are still present on the system
- Standard Sun EOF/EOL Process
- Notices on the front Sun Studio / Developer Tools page at Sun
- Message sent to tools-discuss, desktop-discuss, sfwnv-discuss @os.o

>    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?

libCrun.so.1, which is needed by the Apache Library.

>    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 ...)

That would be me.

> 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...


There are two phases to this:

1. Phase I: before Sun Studio provides command-line switch support for the 
Apache Library, pkg-config will print:

pgk-config --cxxflags stdcxx:

-library=no%Cstd \
	-Qoption ccfe ++boolflag:sunwcch=false \
	-Qoption ccfe -features=gcc \
	-I/usr/include/stdcxx/ansi \
	-I/usr/include/stdcxx \
	-features=anachronisms,except,rtti,\
	export,extensions,nestedaccess,tmplife,\
	tmplrefstatic \
	-instances=global \
	-template=geninlinefuncs \
	-xlang=c99 \
	-D_XOPEN_SOURCE=500 \
	-D_XPG5

pkg-config --ldflags stdcxx:

-library=no%Cstd -lstdcxx

2 Phase II: after implementation of Sun Studio support for the Apache Library 
command-line switch [ updated *.pc files delivered in a patch ]:

pkg-config --cxxflags stdcxx:

[ specific Sun Studio stdcxx compiler flag ] [ example: -library=stdcxx ]

pkg-config --ldflags stdcxx:

[ specific Sun Studio stdcxx compiler flag ] [ example: -library=stdcxx ]

The latter are pure examples -- the actual flags are left entirely at the 
discretion of the DevPro/Tools Group. Not to be construed as an imposition on 
the Tools Group.

>>> 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.

Then i need help with clarifying this. I was under the impression that Garrett 
explicitly asked for this Case not to set a precedent.

--Stefan

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