This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: C++ and useful error messages
- To: "'Phil Edwards'" <pedwards at disaster dot jaj dot com>
- Subject: RE: C++ and useful error messages
- From: pmscott <pmscott at signal dot dera dot gov dot uk>
- Date: Fri, 22 Dec 2000 10:12:30 -0000
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, "libstdc++ at gcc dot gnu dot org" <libstdc++ at gcc dot gnu dot org>
- Organization: DERA
- Reply-To: "pmscott at signal dot dera dot gov dot uk" <pmscott at signal dot dera dot gov dot uk>
On Thursday, December 21, 2000 7:04 PM, Phil Edwards
[SMTP:pedwards@disaster.jaj.com] wrote:
> On Thu, Dec 21, 2000 at 12:05:32PM -0000, pmscott wrote:
> > How about changing:
> >
> > emsg2.C:2: `vector' undeclared (first use this function)
> > emsg2.C:2: (Each undeclared identifier is reported only once for
> > each
> > function it appears in.)
> >
> > to:
> >
> > emsg2.C:2: `vector' undeclared (will not report it again for this
> > function)
>
> If you want to change anything, I would recommend one of
>
> emsg2.C:2: `vector' undeclared (first use in this function)
> emsg2.C:2: `vector' undeclared (first occurrence in this function)
>
I don't mind the wording, it's the use of a two line (three with the
split brackets) error message for one error. I spend a lot of time
stepping past the two extra 'error' lines during initial development,
and it's quite tricky to specify automatically skipping them in every
editor I've tried.
Paul