public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jason@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jason@gcc.gnu.org, nobody@gcc.gnu.org, reichelt@igpm.rwth-aachen.de Subject: Re: c++/2127: namespace problems Date: Fri, 01 Feb 2002 04:03:00 -0000 [thread overview] Message-ID: <20020201120333.26751.qmail@sources.redhat.com> (raw) Synopsis: namespace problems Responsible-Changed-From-To: unassigned->jason Responsible-Changed-By: jason Responsible-Changed-When: Fri Feb 1 04:03:32 2002 Responsible-Changed-Why: got it State-Changed-From-To: analyzed->closed State-Changed-By: jason State-Changed-When: Fri Feb 1 04:03:32 2002 State-Changed-Why: This is not a bug. The candidates considered for the == expression in dummy<S2> are those visible at the point of definition of dummy (only the S1 version) and those in the associated namespace of S2 (also only the S1 version). You must move the S2 version into the namespace. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=2127
next reply other threads:[~2002-02-01 12:03 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-02-01 4:03 jason [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-02-01 7:36 Reichelt 2002-02-01 5:16 Jason Merrill 2001-04-01 0:00 reichelt
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=20020201120333.26751.qmail@sources.redhat.com \ --to=jason@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=reichelt@igpm.rwth-aachen.de \ /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: linkBe 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).