public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nathan@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
martin@loewis.home.cs.tu-berlin.de, nobody@gcc.gnu.org,
rosbacke@nada.kth.se
Subject: Re: c++/88: [parser] ctor/var ambiguity
Date: Tue, 18 Dec 2001 11:51:00 -0000 [thread overview]
Message-ID: <20011218195119.26275.qmail@sources.redhat.com> (raw)
Old Synopsis: GCC do not honor casting when calling constructors from constructors
New Synopsis: [parser] ctor/var ambiguity
State-Changed-From-To: analyzed->suspended
State-Changed-By: nathan
State-Changed-When: Tue Dec 18 11:51:18 2001
State-Changed-Why:
This is a parsing problem, to g++ this looks like
a declaration of local variable Hvec of type Camera2
initialized with (0, 0, 0), but with an extra pair of
parentheses. That extra pair of parentheses are not allowed
by the grammer. Anyway suspended until the new parser
gets merged.[p
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=88
next reply other threads:[~2001-12-18 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-18 11:51 nathan [this message]
2002-12-31 16:50 neil
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=20011218195119.26275.qmail@sources.redhat.com \
--to=nathan@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=martin@loewis.home.cs.tu-berlin.de \
--cc=nobody@gcc.gnu.org \
--cc=rosbacke@nada.kth.se \
/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).