From: "William S. Lear" <rael@zopyra.com>
To: egcs@cygnus.com
Subject: Re: Namespace, the standard library and the C++ Draft Standard
Date: Thu, 09 Apr 1998 08:27:00 -0000 [thread overview]
Message-ID: <13612.53599.881391.278683@lisa.zopyra.com> (raw)
In-Reply-To: <199804081848.LAA14803@atrus.synopsys.com>
On Wed, April 8, 1998 at 11:48:41 (PDT) Joe Buck writes:
>
>> What are the plans on getting egcs up to date to the Draft Standard
>> at least the December 1996 draft?
>
>Work is proceeding to match the final draft. No one is working to
>match the obsolete Dec. 1996 draft, though in most places they are
>not that different.
>
>Martin von Loewis is working on the namespace implementation.
>Mark Mitchell and Kriang Lerdsuwanakij have contributed major
>missing pieces of template functionality.
Speaking of which, Mark Mitchell contributed patches for a template
problem I reported long ago. I never saw these mentioned as being
included in egcs. How can one tell which patches have been accepted,
and which remain to be?
Bill
next prev parent reply other threads:[~1998-04-09 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-08 6:47 Dirk Broer
1998-04-08 17:25 ` Joe Buck
1998-04-09 8:27 ` William S. Lear [this message]
1998-04-09 10:53 ` Jeffrey A Law
1998-04-09 14:17 ` Joe Buck
1998-04-10 20:10 Mike Stump
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=13612.53599.881391.278683@lisa.zopyra.com \
--to=rael@zopyra.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).