public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Carlo Wood <carlo@runaway.xs4all.nl>
Cc: egcs@cygnus.com (egcs@cygnus.com)
Subject: Re: Release status
Date: Thu, 03 Sep 1998 05:16:00 -0000	[thread overview]
Message-ID: <10236.904756200@hurl.cygnus.com> (raw)
In-Reply-To: <199809021654.SAA06376@jolan.ppro>

  In message < 199809021654.SAA06376@jolan.ppro >you write:
  > | http://egcs.cygnus.com/egcs-1.1/egcs-1.1.html
  > | 
  > | Has the current announcement.  I do not expect it to change significantly
  > .
  > 
  > In http://egcs.cygnus.com/egcs-1.1/c++features.html
  > there is a section saying:
  > 
  > 
  >   Still not supported:
  > 
  >        + Member class templates.
  >        + Template friends.
  > 
  > 
  > I believe this to be incorrect?
  > At least Template friends are supported.
Both are supported.  You're reading old news.

The NEWS file is just that -- accumulated NEWS over the years.  The
info at the top always overrides later info.  In this case you'll find

*** Changes since EGCS 1.0:

[ ... ]

* Massive template improvements:
  + member template classes are supported.
  + template friends are supported.
  + template template parameters are supported.
  + local classes in templates are supported.
  + lots of bugs fixed.

[ ... ]

*** Changes in EGCS 1.0:

[ ... ]

  Still not supported:

     + Member class templates.
     + Template friends.

jeff

  reply	other threads:[~1998-09-03  5:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-02  1:50 Jeffrey A Law
1998-09-03  4:22 ` Carlo Wood
1998-09-03  5:16   ` Jeffrey A Law [this message]
1998-09-03  5:16 ` SL Baur
  -- strict thread matches above, loose matches on Subject: below --
1997-10-31  6:27 Release Status Max Lawson
1997-10-30 20:16 Jeffrey A Law
1997-10-30 14:17 ` Joe Buck
1997-10-30 22:23 ` Oleg Krivosheev
1997-10-31 15:51   ` 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=10236.904756200@hurl.cygnus.com \
    --to=law@cygnus.com \
    --cc=carlo@runaway.xs4all.nl \
    --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).