public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: kparz@iastate.edu
To: gcc-gnats@gcc.gnu.org
Subject: c++/7844: Function declarations parsed incorrectly
Date: Thu, 05 Sep 2002 15:36:00 -0000 [thread overview]
Message-ID: <200209052230.g85MU0Y0092124@arcturus.student.iastate.edu> (raw)
>Number: 7844
>Category: c++
>Synopsis: Function declarations parsed incorrectly
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: rejects-legal
>Submitter-Id: net
>Arrival-Date: Thu Sep 05 15:36:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: kparz
>Release: 3.3 20020905 (experimental)
>Organization:
>Environment:
System: FreeBSD arcturus.student.iastate.edu 4.6-STABLE FreeBSD 4.6-STABLE #15: Sat Aug 24 23:25:48 CDT 2002 kparz@arcturus.student.iastate.edu:/usr/obj/usr/src/sys/ARCTURUS i386
host: i386-unknown-freebsd4.6
build: i386-unknown-freebsd4.6
target: i386-unknown-freebsd4.6
configured with: ../gcc/configure --prefix=/u/gcc-20020905 --enable-languages=c,c++,f77
>Description:
Ambiguity in function declarations is resolved incorrectly.
See ISO/IEC 14882:1998(E), 8.2 p7
>How-To-Repeat:
# 1 "parse.cc"
# 1 "<built-in>"
# 1 "<command line>"
# 1 "parse.cc"
typedef int I;
void foo(int(I));
void (*bar)(int (*)(int)) = &foo;
>Fix:
Use the other style of function declarators (with *), i.e.
void foo(int (*)(I));
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-09-05 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 15:36 kparz [this message]
2002-09-13 9:03 lerdsuwa
2002-09-13 9:26 Krzysztof Parzyszek
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=200209052230.g85MU0Y0092124@arcturus.student.iastate.edu \
--to=kparz@iastate.edu \
--cc=gcc-gnats@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).