From: Jason Merrill <jason@cygnus.com>
To: egcs@cygnus.com
Subject: Re: libg++?
Date: Sat, 30 Aug 1997 21:24:56 -0000 [thread overview]
Message-ID: <199708301807.LAA32214@icarus.icarus.com> (raw)
Message-ID: <19970830212456.prBwahiQpRA5VulfxfEjp1DcQGYuH9Zpkrzi99R9OIU@z> (raw)
In-Reply-To: libg++?
>>>>> Chip Salzenberg writes:
> Could someone please explain the relationships among libio, libstd++, and
> libg++? And given all the activity in C++, could someone explain why
> libg++ hasn't been modified since 14 February 1997 (version 2.8.0b6)?
libio is Per's iostream code (and stdio, but most targets don't use that).
libstdc++ is the rest of the standard library.
libg++ is Doug Lea's old C++ class library.
The libg++ directory hasn't been modified because it doesn't relate to the
standard, and we're not interested in maintaining it anymore (I think;
right, Ulrich?). Someone else is welcome to take it over.
Jason
next reply other threads:[~1997-08-30 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-30 12:00 Stephen Williams [this message]
1997-08-30 19:18 ` fixing the c++/f77 circular dependency Joel Sherrill
1997-08-30 19:18 ` Incorrect i960 linker config Joel Sherrill
1997-08-30 19:18 ` include hackery Bruce Korb
1997-08-30 21:24 ` libg++? Jason Merrill
1997-09-01 10:27 ` Incorrect i960 linker config Jeffrey A Law
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199708301807.LAA32214@icarus.icarus.com \
--to=jason@cygnus.com \
--cc=egcs@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).