public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: stip@mathematik.uni-ulm.de
To: gcc-gnats@gcc.gnu.org
Subject: c++/10337: "ambiguous overload"-error for non-ambiguous situation
Date: Mon, 07 Apr 2003 12:06:00 -0000	[thread overview]
Message-ID: <20030407120546.28136.qmail@sources.redhat.com> (raw)


>Number:         10337
>Category:       c++
>Synopsis:       "ambiguous overload"-error for non-ambiguous situation
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Mon Apr 07 12:06:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Alexander Stippler
>Release:        unknown-1.0
>Organization:
>Environment:
Solaris 2.9
gcc 3.2
>Description:
convtest.cc:25: ambiguous overload for `B& = C&' operator
convtest.cc:9: candidates are: void B::operator=(const A&)
convtest.cc:10:                void B::operator=(const B&)

The second assignment operator (line 10) has to be chosen IMO because of section 13.3.3.2/3 of the standard. Compiles with gcc 3.3 / 3.4 but emits warnings (why?)


class A {
    public:
        A() {}
};

class B : public A {
    public:
        B() {}
        void operator=(const A& b) {}
        void operator=(const B& b) {}
};

class C {
    public:
        C() {}
        operator B &() { return _b; }
        operator const B &() const { return _b; }

        B _b;
};

int main() {
    B b;
    C c;
    b = c;
}
>How-To-Repeat:
g++ convtest.cc
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-04-07 12:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07 12:06 stip [this message]
2003-04-10 14:32 bangerth
2003-04-20 12:52 nathan
2003-04-24 16:31 nathan

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=20030407120546.28136.qmail@sources.redhat.com \
    --to=stip@mathematik.uni-ulm.de \
    --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: 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).