public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Krzysztof Parzyszek <kparz@iastate.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7844: Function declarations parsed incorrectly
Date: Fri, 13 Sep 2002 09:26:00 -0000	[thread overview]
Message-ID: <20020913162601.12761.qmail@sources.redhat.com> (raw)

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

From: Krzysztof Parzyszek <kparz@iastate.edu>
To: lerdsuwa@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   kparz@iastate.edu, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/7844: Function declarations parsed incorrectly
Date: Fri, 13 Sep 2002 11:15:23 -0500

 On Fri, Sep 13, 2002 at 04:03:47PM -0000, lerdsuwa@gcc.gnu.org wrote:
 > Synopsis: Function declarations parsed incorrectly
 > 
 > State-Changed-Why:
 >     Not a bug.
 >     The declaration of 'foo' is parsed as
 >       void foo(int I)
 >     i.e., a function accepting an integer parameter named 'I'.
 >     The 'I' inside 'foo' hides the global typedef 'I'.
 
 
 7 Another ambiguity arises in a parameter-declaration-clause of a  func-
   tion  declaration,  or in a type-id that is the operand of a sizeof or
   typeid operator, when a type-name is nested in parentheses.   In  this
   case,  the  choice  is  between the declaration of a parameter of type
   pointer to function and the declaration of a parameter with  redundant
   parentheses  around  the declarator-id.  The resolution is to consider
   the type-name as a simple-type-specifier rather than a  declarator-id.
   [Example:
           class C { };
           void f(int(C)) { } // void f(int (*fp)(C c)) { }
                              // not: void f(int C);
 
 
 -- 
 <>> kristof@swissmail.org <Krzysztof Parzyszek>    9/2/2002
 <<> "If you can't convince them, confuse them" -- HS Truman


             reply	other threads:[~2002-09-13 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-13  9:26 Krzysztof Parzyszek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-13  9:03 lerdsuwa
2002-09-05 15:36 kparz

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=20020913162601.12761.qmail@sources.redhat.com \
    --to=kparz@iastate.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).