From: Joe Buck <jbuck@synopsys.com>
To: egcs@cygnus.com
Subject: Re: libg++?
Date: Sat, 30 Aug 1997 22:12:21 -0000 [thread overview]
Message-ID: <9708302212.AA20985@beeblebrox-84.synopsys.com> (raw)
Message-ID: <19970830221221.FSPCSPvoNmTs-JQbytBzvFDJ7Du_cxNDdOpGq5NlH3M@z> (raw)
In-Reply-To: u9sovr2wk7.fsf@yorick.cygnus.com
> 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.
The only parts of old libg++ that I think are that interesting anymore are
the random number classes: there's a nice scheme to generate a variety of
types of random numbers with different distributions. I think these
originally came from Dirk Grunwald's Awesime project, not from Doug Lea.
Ptolemy used them.
Much of the rest of libg++ I would consider obsolete: String, Complex,
the containers, especially now that we have the SGI hashing classes and
singly linked list. Just the same, some people still use it, so we can
put it out and call it deprecated.
next reply other threads:[~1997-08-30 22:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-30 22:12 Weiwen Liu [this message]
1997-08-30 22:12 ` libg++? Joe Buck
1997-08-31 0:09 egcs-970828 install Jim Wilson
1997-09-02 3:33 ` Ian Lance Taylor
1997-08-31 18:57 Joe Buck
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=9708302212.AA20985@beeblebrox-84.synopsys.com \
--to=jbuck@synopsys.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).