[Bug libstdc++/33831] [4.3 Regression] Revision 129442 breaks libstc++ API

[bkoz at gcc dot gnu dot org]

------- Comment #18 from bkoz at gcc dot gnu dot org  2008-01-16 18:46 -------

The ammount of breakage for this change is IMHO tolerable and will within the
tolerances of other breakages that nobody is talking about reverting, and
furthermore solutions for the API change are well documented. Certainly, the
demonstrated breakage for the pre-iso header removal in fedora builds is about
8 packages, less than most of the individual FE changes in either 4.2 or 4.3. 

I believe there is a bit of a bias here, in that it's OK to make FE changes,
but even well-documented and warned lib changes are not ok? What's up with
that? I assert the right to make API changes, including removal of deprecated
items.

I believe my rationale in #6 has been missed by all. Please directly respond to
this, and tell me why it's ok to remove flags and things like max/min in the
C++FE, and not ok to remove deprecated headers in libstdc++.

I am opposed to wholesale re-instatement of the pre-iso headers, and would like
to close this as WONTFIX. From fedora build failure analysis, only two are
important: iostream.h and fstream.h. If i am to be over-ruled on this issue,
then please only reinstate these two.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33831