From: Joe Buck <jbuck@synopsys.com>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: Matt Austern <austern@apple.com>,
Gabriel Dos Reis <gdr@integrable-solutions.net>,
Giovanni Bajo <giovannibajo@libero.it>,
gcc@gcc.gnu.org
Subject: Re: C++ extension "cast-as-lvalues": time to deprecate?
Date: Fri, 09 May 2003 21:01:00 -0000 [thread overview]
Message-ID: <20030509140051.A27259@synopsys.com> (raw)
In-Reply-To: <3EBBF4AB.3010002@codesourcery.com>; from nathan@codesourcery.com on Fri, May 09, 2003 at 07:34:19PM +0100
On Fri, May 09, 2003 at 07:34:19PM +0100, Nathan Sidwell wrote:
> Matt Austern wrote:
>
> > We said it was deprecated in the documentation, but we never enforced
> > that with a warning. I think the schedule for removal will have to
> > look something like this:
> > - Next release: put in a warning for this extension, and allow users
> > to turn it off with a switch.
> > - The release after that: don't allow users to turn the warning off.
> > - Finally, in the next release: remove it entirely.
> >
> > I could imagine doing this over the course of two releases instead
> > of three, but two is the absolute minimum.
> Normal practice for g++ at least appears to be two, add a warning in
> release N, remove it in N+1
There's a somewhat different issue here, though: what about strictly
conforming programs that malfunction because of the extension, in a way
that is surprising to the user? Do we have to keep miscompiling them
for two more releases?
next prev parent reply other threads:[~2003-05-09 21:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 23:54 Giovanni Bajo
2003-05-09 4:06 ` Fergus Henderson
2003-05-09 8:34 ` Joseph S. Myers
2003-05-09 12:38 ` Fergus Henderson
2003-05-09 12:41 ` Gabriel Dos Reis
2003-05-09 22:12 ` Neil Booth
2003-05-09 22:39 ` Joseph S. Myers
2003-05-09 12:49 ` Giovanni Bajo
2003-05-09 14:06 ` Fergus Henderson
2003-05-09 6:55 ` Gabriel Dos Reis
2003-05-09 17:15 ` Joe Buck
2003-05-09 17:45 ` Gabriel Dos Reis
2003-05-09 18:13 ` Matt Austern
2003-05-09 18:34 ` Nathan Sidwell
2003-05-09 18:48 ` Giovanni Bajo
2003-05-09 21:01 ` Joe Buck [this message]
2003-05-09 23:21 ` Mark Mitchell
2003-05-12 16:30 ` Joe Buck
2003-05-12 16:42 ` Mark Mitchell
2003-05-12 17:11 ` Joe Buck
2003-05-12 17:58 ` Fergus Henderson
2003-05-16 1:15 ` Giovanni Bajo
2003-05-16 1:23 ` 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=20030509140051.A27259@synopsys.com \
--to=jbuck@synopsys.com \
--cc=austern@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=giovannibajo@libero.it \
--cc=nathan@codesourcery.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).