public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Giovanni Bajo" <giovannibajo@libero.it>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/4337: [2003-01-01]c++ ignores cast operator
Date: Wed, 14 May 2003 00:46:00 -0000	[thread overview]
Message-ID: <20030514004600.21367.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/4337; it has been noted by GNATS.

From: "Giovanni Bajo" <giovannibajo@libero.it>
To: "Bogdanov, Serge" <serge.bogdanov@intel.com>,
	<gcc-bugs@gcc.gnu.org>,
	<gcc-prs@gcc.gnu.org>,
	<nobody@gcc.gnu.org>,
	<gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: c++/4337: [2003-01-01]c++ ignores cast operator
Date: Wed, 14 May 2003 02:36:09 +0200

 Bogdanov, Serge <serge.bogdanov@intel.com> wrote:
 
 >       The latest analysis by Giovanni solves one mystery, but there is
 > another one in the same bug report: if the cast operator is removed,
 > compiler produces warnings.
 >
 >>>> g++ -o a a.cpp
 > a.cpp: In function `int main()':
 > a.cpp:27: warning: choosing `A2::operator A1()' over `A1::A1(const A&)'
 > a.cpp:27: warning:   for conversion from `A2' to `A1'
 > a.cpp:27: warning:   because conversion sequence for the argument is
 better
 
 And what would the problem be? If you remove the cast operator, you end up
 with "a2 = a1" which obviously selects the cast operator. The compiler is
 just warning you about the possible ambiguity, but it's choosing the right
 path.
 
 Giovanni Bajo
 


             reply	other threads:[~2003-05-14  0:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14  0:46 Giovanni Bajo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-13 21:19 Bogdanov, Serge
2003-05-05  1:14 giovannibajo

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=20030514004600.21367.qmail@sources.redhat.com \
    --to=giovannibajo@libero.it \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).