This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/14830] compiler incorrectly diagnoses ambigous operator overload
- From: "iker at research dot att dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 3 Apr 2004 19:14:21 -0000
- Subject: [Bug c++/14830] compiler incorrectly diagnoses ambigous operator overload
- References: <20040403004706.14830.iker@research.att.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From iker at research dot att dot com 2004-04-03 19:14 -------
Subject: Re: compiler incorrectly diagnoses ambigous operator
overload
It seems more natural (at least to me) to have the
compiler select the direct conversion to string for
the assignment instead of considering the longer
route as well. Is there some fundamental reason why
it considers the direct and indirect conversions as
equivalent?
Regards,
Iker
pinskia at gcc dot gnu dot org wrote:
> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-04-03 15:54 -------
> Invalid as float can be converted to a char and string well can be converted to string, so the ambigous
> error is correct.
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14830