public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: theonetruekenny@yahoo.com To: gcc-gnats@gcc.gnu.org Subject: c++/2294: using declaration confusion Date: Thu, 15 Mar 2001 12:56:00 -0000 [thread overview] Message-ID: <20010315204849.11766.qmail@sourceware.cygnus.com> (raw) >Number: 2294 >Category: c++ >Synopsis: using declaration confusion >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Thu Mar 15 12:56:00 PST 2001 >Closed-Date: >Last-Modified: >Originator: Kenny Simpson >Release: gcc version 3.0 20010313 (prerelease) >Organization: >Environment: online compiler >Description: >From the example in section 7.3.3 12 of the 1997 draft, gcc complains about the "using C::f" declaration. >How-To-Repeat: from http://anubis.dkuug.dk/jtc1/sc22/open/n2356/dcl.html: namespace B { void f(int); void f(double); } namespace C { void f(int); void f(double); void f(char); } void h() { using B::f; // B::f(int) and B::f(double) using C::f; // C::f(int), C::f(double), and C::f(char) f('h'); // calls C::f(char) f(1); // error: ambiguous: B::f(int) or C::f(int) ? void f(int); // error: // f(int) conflicts with C::f(int) and B::f(int) } >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2001-03-15 12:56 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010315204849.11766.qmail@sourceware.cygnus.com \ --to=theonetruekenny@yahoo.com \ --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: 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).