This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Noisy when choosing T::operator Type() vs T::op constType() const
- To: Gabriel dot Dos-Reis at cmla dot ens-cachan dot fr
- Subject: Re: Noisy when choosing T::operator Type() vs T::op constType() const
- From: Mark Mitchell <mark at codesourcery dot com>
- Date: Sun, 17 Sep 2000 22:49:04 -0700
- Cc: jimc at math dot ucla dot edu, gcc-bugs at gcc dot gnu dot org, Jason Merrill <jason at cygnus dot com>
- Organization: CodeSourcery, LLC
- References: <flr96ifzbc.fsf@sel.cmla.ens-cachan.fr>
>>>>> "Gabriel" == Gabriel Dos Reis <Gabriel.Dos-Reis@cmla.ens-cachan.fr> writes:
Gabriel> To tell the truth, I don't find the diagnostic really
Gabriel> helpful -- if we were to include it, then there is no
Gabriel> reason we should left out other C++ traps.
I agree. Besides, the wording isn't really clear enough to enable
most people to figure out what's going on. It couldn't possibly be,
since the rule involved is obscure, and somewhat hard to comprehend.
Alexandre says that we introduced this warning to reduce the number of
times users complained about what they perceived as incorrect
behavior. I think that we should just grin and bear it; uneducated
users are a part of customer support. A FAQ entry would be useful, of
course.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com