From: Phil Edwards <phil@jaj.com>
To: Ed Parcell <ed@edparcell.com>
Cc: gcc@gnu.org
Subject: Re: bug in libstdc++ bitset
Date: Mon, 19 Aug 2002 07:57:00 -0000 [thread overview]
Message-ID: <20020819105712.A21692@disaster.basement.lan> (raw)
In-Reply-To: <1029762313.2239.2.camel@tedlinux>
On Mon, Aug 19, 2002 at 02:05:12PM +0100, Ed Parcell wrote:
> Hi,
>
> Sorry that this is almost definitely the wrong place to send this to.
http://gcc.gnu.org/lists.html
> I am using libstdc++ in the debian package libstdc++2.10, which has the
> description "This is not a final release, but taken from the CVS
> gcc-2_95-branch
> (dated 2001-10-02)".
The 2.x series hasn't been maintained in quite some time. The 3.x library
is a complete rewrite.
Phil
--
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002
prev parent reply other threads:[~2002-08-19 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 6:05 Ed Parcell
2002-08-19 6:30 ` Andrew Pinski
2002-08-19 7:57 ` Phil Edwards [this message]
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=20020819105712.A21692@disaster.basement.lan \
--to=phil@jaj.com \
--cc=ed@edparcell.com \
--cc=gcc@gnu.org \
/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).