From: Mark Mitchell <mark@codesourcery.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: Joe Buck <Joe.Buck@synopsys.com>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: gcc 3.2.1 draft release notes, 3rd draft
Date: Tue, 15 Oct 2002 11:33:00 -0000 [thread overview]
Message-ID: <59720000.1034701726@warlock.codesourcery.com> (raw)
In-Reply-To: <200210151621.g9FGLIF19813@piper.synopsys.com>
> Then how about adding a rule something like the following to the bison
> grammar (yes, I know these are the wrong terminal names, but the idea
> should be clear):
>
> TYPEDEF ID '=' error ';'
> { error("Please use __typeof() instead");}
Along these lines, one could perhaps even do the transformation at that
point.
TYPEDEF ID = expression ;
{ /* Do whatever you do for the typeof case. */ }
> However, I don't understand why the extension was removed. If its
> presence makes it harder to parse valid C/C++ the removal might be
> justified.
The extension was removed because it's been broken forever and nobody
complained. It thus seemed an opportune time to get rid of a language
extension -- they all create problems in one way or another -- and
this one was both apparently unused and had as an equivalent form.
If people think that's a bad decision, we can go back and try to do
the above transformation. My sentiment is that -- given that there's
considerable evidence that nobody uses this extension -- our time is
best spent elsewhere.
On the other hand, as the approver of the patch, I'm responsible; I'll
attempt the transformation patch if people want that.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2002-10-15 17:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 17:38 Joe Buck
2002-10-15 1:27 ` Mark Mitchell
2002-10-15 10:10 ` Joe Buck
2002-10-15 11:33 ` Mark Mitchell [this message]
2002-10-15 19:11 ` Zack Weinberg
2002-10-15 21:19 ` Joe Buck
2002-10-18 4:48 ` Zack Weinberg
2002-10-18 5:17 ` Mark Mitchell
2002-10-18 7:42 ` John Marshall
2002-10-22 17:20 ` Zack Weinberg
2002-10-15 9:02 ` Alexandre Oliva
2002-10-15 9:18 ` Gabriel Dos Reis
2002-10-15 5:19 Reichelt
2002-10-15 13:00 Ulrich Weigand
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=59720000.1034701726@warlock.codesourcery.com \
--to=mark@codesourcery.com \
--cc=Joe.Buck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.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).