From: John Love-Jensen <eljay@adobe.com>
To: Alexander Werth <alexander.werth@gmx.de>,
GCC-help <gcc-help@gcc.gnu.org>
Subject: Re: namespace and class within with similar name
Date: Tue, 05 Aug 2008 11:44:00 -0000 [thread overview]
Message-ID: <C4BDA724.32C31%eljay@adobe.com> (raw)
In-Reply-To: <1217890908.21247.17.camel@Jiminy>
Hi Alexander,
> Shouldn't it be clear that I wan't to access class L in
> namespace S and not some L of class S in namespace S ?
It appears that when you injected the identifiers from namespace S into the
global namespace, the ::S::L is ambiguous between namespace S and class S
which both are (now) in the global namespace.
The compiler is going down the class S path.
I think that's a bug.
Not that I can cite chapter/verse of ISO 14882, rather I just tested against
the EDG front end, and EDG accepted the code. (I have strong confidence
that the EDG front end is fully compliant with ISO 14882.)
> Any idea besides complaining about why I want to do this at all ? ;)
I think you should file a bug. Maybe it will get fixed in GCC 4.4, and if
not, probably by 4.5.
http://gcc.gnu.org/bugs.html
Sincerely,
--Eljay
prev parent reply other threads:[~2008-08-05 11:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 23:03 Alexander Werth
2008-08-05 11:44 ` John Love-Jensen [this message]
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=C4BDA724.32C31%eljay@adobe.com \
--to=eljay@adobe.com \
--cc=alexander.werth@gmx.de \
--cc=gcc-help@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).