public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: stip@mathematik.uni-ulm.de
To: gcc-gnats@gcc.gnu.org
Cc: lehn@mathematik.uni-ulm.de
Subject: c++/10380: warning about "choosing ... over ..." when there is no choice
Date: Fri, 11 Apr 2003 19:16:00 -0000	[thread overview]
Message-ID: <20030411191355.22835.qmail@sources.redhat.com> (raw)


>Number:         10380
>Category:       c++
>Synopsis:       warning about "choosing ... over ..." when there is no choice
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Apr 11 19:16:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     stip@mathematik.uni-ulm.de
>Release:        unknown-1.0
>Organization:
>Environment:
gcc 3.2 on Solaris 2.9
>Description:
gcc produces warning about chosing one conversion operator over another in the following example where there is only one correct choice:

struct A
{
};

struct B : public A
{
};

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

int
main()
{
    C c;

    A a;
    B b;

    a = c;
    b = c;

    return 0;
}

According to the standard IMO there is no reason to complain but the second conversion operator B() has
to be chosen in both assignments. There is no way to (correctly) apply the first conversion operator, so why
warning about the possibility?
There is no switch to turn exactly this warning off what makes it even worse.
>How-To-Repeat:
g++ 
>Fix:

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


             reply	other threads:[~2003-04-11 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-11 19:16 stip [this message]
2003-04-11 19:44 bangerth
2003-04-20 13:39 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=20030411191355.22835.qmail@sources.redhat.com \
    --to=stip@mathematik.uni-ulm.de \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=lehn@mathematik.uni-ulm.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: 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).