public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net> 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 04:06:00 -0000 [thread overview] Message-ID: <20030208040601.12002.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9621; it has been noted by GNATS. From: Gabriel Dos Reis <gdr@integrable-solutions.net> To: bangerth@dealii.org 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: 08 Feb 2003 05:03:09 +0100 bangerth@dealii.org writes: | Synopsis: const int typedef is rejected | | State-Changed-From-To: open->feedback | State-Changed-By: bangerth | State-Changed-When: Sat Feb 8 00:22:54 2003 | State-Changed-Why: | Fixed in 3.4: it accepts both typedefs. | | I'm surprised that this is legal at all. The standard says | that typedef expressions need to "contain" the typedef | keyword, but the examples only show it as in the form | typedef type1 type2; | | Can some language lawyer comment on whether and why | type1 typedef type2; | is legal syntax? It is. See a recent discussion on comp.std.c++ where I gave detailed references. Basically it boils down to the clause 7; section 7.1. decl-specifiers can appear in *any* order -- that is one of the reasons why grokdeclarator() is so weird. -- Gaby
next reply other threads:[~2003-02-08 4:06 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-08 4:06 Gabriel Dos Reis [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 0:56 Wolfgang Bangerth 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=20030208040601.12002.qmail@sources.redhat.com \ --to=gdr@integrable-solutions.net \ --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: linkBe 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).