[Bug c++/22256] diagnostic shows wrong type for cast operator

2007-08-06 Thread pcarlini at suse dot de
--- Comment #6 from pcarlini at suse dot de 2007-08-06 11:52 --- The subtle issue here is that this specific error message should be emitted *only* when the incorrectly specified return type doesn't match, thus a plain error instead of a pedwarn: case sfk_conversion: if (type

[Bug c++/22256] diagnostic shows wrong type for cast operator

2005-06-30 Thread pinskia at gcc dot gnu dot org
-- What|Removed |Added Severity|normal |enhancement Keywords||diagnostic Known to fail|

[Bug c++/22256] diagnostic shows wrong type for cast operator

2005-06-30 Thread gdr at integrable-solutions dot net
--- Additional Comments From gdr at integrable-solutions dot net 2005-06-30 20:56 --- Subject: Re: diagnostic shows wrong type bangerth at dealii dot org [EMAIL PROTECTED] writes: | Confirmed. Also happens with 3.3.x. I think this happens because when the C++ front-end finds that a

[Bug c++/22256] diagnostic shows wrong type for cast operator

2005-06-30 Thread igodard at pacbell dot net
--- Additional Comments From igodard at pacbell dot net 2005-06-30 21:48 --- Gabriel: no, it also happens with any pointer: struct node { float*operator float*(); }; gets you: foo.cc:1: error: operator `float*' declared to return `float' And similarly for other types

Re: [Bug c++/22256] diagnostic shows wrong type for cast operator

2005-06-30 Thread Gabriel Dos Reis
igodard at pacbell dot net [EMAIL PROTECTED] writes: | Gabriel: no, it also happens with any pointer: | | struct node { float*operator float*(); }; | | gets you: | | foo.cc:1: error: operator `float*' declared to return `float' Alright, that was a wrong guess. -- Gaby

[Bug c++/22256] diagnostic shows wrong type for cast operator

2005-06-30 Thread gdr at integrable-solutions dot net
--- Additional Comments From gdr at integrable-solutions dot net 2005-06-30 22:11 --- Subject: Re: diagnostic shows wrong type for cast operator igodard at pacbell dot net [EMAIL PROTECTED] writes: | Gabriel: no, it also happens with any pointer: | | struct node { float*