public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9621: const int typedef is rejected
Date: Sat, 08 Feb 2003 00:56:00 -0000	[thread overview]
Message-ID: <20030208005600.25672.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/9621; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
Cc: gcc-bugs@gcc.gnu.org, <patrick.rabau@gs.com>, <gcc-gnats@gcc.gnu.org>
Subject: Re: c++/9621: const int typedef is rejected
Date: Fri, 7 Feb 2003 18:46:10 -0600 (CST)

 > >     Can some language lawyer comment on whether and why
 > >       type1 typedef type2;
 > >     is legal syntax?
 > 
 > No, it isn't. typedef is a decl-specifier. They are only allowed as a
 > sequence at the start of a simple-declaration:
 
 So it's a bug that gcc accepts it in C++. In a strange sense, it's then 
 even a regression that it previously only accepted the version without 
 "const" and now accepts both with and without const :-)
 
 I'll change the synopsis of the report in a minute. Thanks for your 
 clarification.
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-02-08  0:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-08  0:56 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-08 13:26 Falk Hueffner
2003-02-08  4:16 Gabriel Dos Reis
2003-02-08  4:06 Gabriel Dos Reis
2003-02-08  4:06 Gabriel Dos Reis
2003-02-08  0:46 Falk Hueffner
2003-02-08  0:22 bangerth
2003-02-07 23:56 patrick.rabau

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=20030208005600.25672.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).