This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Improving C++ error output?

From: Neil Booth <neil at daikokuya dot co dot uk>
To: Craig Rodrigues <rodrigc at attbi dot com>
Cc: "Randy.Dunlap" <rddunlap at osdl dot org>, gcc at gcc dot gnu dot org
Date: Sat, 21 Dec 2002 08:30:23 +0000
Subject: Re: Improving C++ error output?
References: <200212202220.gBKMKGf18370@piper.synopsys.com> <Pine.LNX.4.33L2.0212201435360.1703-100000@dragon.pdx.osdl.net> <20021220195805.A3022@attbi.com>

Craig Rodrigues wrote:-

> One way that GCC could make this type of system much easier to
> develop is to format error messages consistently so that they can be parsed.
> Right now, the formatting and content of GCC error messages seems
> to be ad hoc. 

I've been pushing for this for a while, since we want to move to
caret diagnostics, which will be multiline, and quote the relevant
line of the source code.

Neil.

References:
- Re: Improving C++ error output?
  - From: Joe Buck
- Re: Improving C++ error output?
  - From: Randy.Dunlap
- Re: Improving C++ error output?
  - From: Craig Rodrigues

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]