gcc-2.95 and SGI STL 3.2

[Jeffrey A Law]

  In message < 19990621032446.2159.qmail@deer >you write:
  >   -  gcc 3.0 is an "event" that many people will expect to require
  >      recompiling anyway, so things like a new STL could happen there.
Yup.

  >   -  gcc 2.95 might be "big enough" without the new STL for the gcc
  >      community, especially those users who have not already switched
  >      to EGCS, and thus will see it as the "next" version after 2.8.1.
  >      (I know basically nothing about the STL issues, and therefore have
  >      no opinion on them.)
gcc-2.95 certainly a big jump for those who haven't already switched to the
egcs line of development.  Remember the C++ compiler in gcc-2.8 is old, like
a full 2 years old.  

gcc-2.95 is much less of a jump for those who have been tracking the egcs-1.0,
egcs-1.1 releases.  While I've been told gcc-2.95 will be binary incompatible
with egcs-1.1.2 due to C++ issues, I've actually yet to have any problems 
with linking egcs-1.1.2 C++ libraries with gcc-2.95 C++ code.

  >   -  Someday g77 really needs to break away from libf2c, and define
  >      its own library, libg77.  3.0 would be great for this, but I doubt
  >      it'll happen -- the 0.6 rewrite (which involves the front end,
  >      not the run-time library) is a big-enough task for me now.  That
  >      means libg77 would be a gcc 4.0 item, though possibly we could
  >      decide on it being a 3.X item, since we still speak of g77 being
  >      in "beta".
I think replacing libf2c with libg77 would be a reasonable item to add in a
3.x release if we do not get it into gcc-3.0.

jeff