This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: [Bug libstdc++/15910] can't compile self defined void distance(std::vector<T>, std::vector<T>)
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: gcc-bugzilla at gcc dot gnu dot org
- Cc: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 9 Aug 2005 22:48:59 -0400
- Subject: Re: [Bug libstdc++/15910] can't compile self defined void distance(std::vector<T>, std::vector<T>)
- References: <20040610143911.15910.king.benjamin@mh-hannover.de> <20050810024101.27049.qmail@sourceware.org>
On Aug 9, 2005, at 10:41 PM, adah at netstd dot com wrote:
Passing this information to the user is difficult, unless GCC emits a
diagnostic message to help users do so, as GCC is currently doing on
the
missing of `typename'.
even then as I said before when it comes down to it, nobody reads those
messages as they think their code is correct.
See my example when sequence points, we do warn about it in 4.0.0 and
above
(for C++; for C, we have warned since at least 3.0.4) and people still
file bugs.
Another example of where people don't read is the changes page, which
describes
changes to the compiler which could hinder (or benefit) them. One
example is
the change in the namelookup for templates to be more towards the
standard. That
example shows that we still get bug reports so even with a better error
message,
people will have something to complain about.
-- Pinski