public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/11828] [3.4 regression] qualified dependent name looked up too early
Date: Tue, 11 May 2004 18:38:00 -0000 [thread overview]
Message-ID: <20040510195125.14740.qmail@sourceware.org> (raw)
In-Reply-To: <20030806091852.11828.benko@sztaki.hu>
------- Additional Comments From jason at gcc dot gnu dot org 2004-05-10 19:51 -------
[temp.nondep] is only relevant if you assume that n::f is a non-dependent name,
which I am not willing to assume. I believe it is dependent under the principle
outlined in [temp.dep]:
In an
expression of the form:
postfix-expression ( expression-listopt )
where the postfix-expression is an identifier, the identifier denotes
a dependent name if and only if any of the expressions in the
expression-list is a type-dependent expression (_temp.dep.expr_).
In this testcase, the postfix-expression is not a plain identifier, but I
believe that it should be handled the same way, and that this is an oversight in
the standard. EDG seem to agree with me, as 3.4 accepts this testcase and those
from the various duplicates of this bug.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11828
next prev parent reply other threads:[~2004-05-10 19:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 9:18 [Bug c++/11828] New: " benko at sztaki dot hu
2003-08-06 14:39 ` [Bug c++/11828] " bangerth at dealii dot org
2003-08-07 7:06 ` benko at sztaki dot hu
2003-08-07 13:20 ` bangerth at dealii dot org
2003-08-07 13:21 ` bangerth at dealii dot org
2003-08-11 7:04 ` benko at sztaki dot hu
2003-08-11 21:00 ` janis187 at us dot ibm dot com
2003-08-21 6:02 ` mmitchel at gcc dot gnu dot org
2004-04-26 12:57 ` pinskia at gcc dot gnu dot org
2004-05-11 18:34 ` jason at gcc dot gnu dot org
2004-05-11 18:38 ` jason at gcc dot gnu dot org [this message]
2004-05-11 18:53 ` [Bug c++/11828] [3.4/3.5 " pinskia at gcc dot gnu dot org
2004-05-11 18:56 ` pinskia at gcc dot gnu dot org
2004-05-11 19:23 ` bangerth at dealii dot org
2004-05-11 19:24 ` jason at redhat dot com
2004-05-11 19:37 ` bangerth at dealii dot org
2004-06-03 22:29 ` pinskia at gcc dot gnu dot org
2004-06-10 20:04 ` jason at gcc dot gnu dot org
2004-10-28 13:53 ` [Bug c++/11828] [3.4/4.0 " pinskia at gcc dot gnu dot org
2005-02-21 19:12 ` smcpeak at cs dot berkeley dot edu
2005-03-03 22:55 ` pinskia at gcc dot gnu dot org
2005-03-04 5:00 ` smcpeak at cs dot berkeley dot edu
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=20040510195125.14740.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).