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: feature request

From: Joe Buck <Joe dot Buck at synopsys dot COM>
To: David Skinner <dskinner at nersc dot gov>
Cc: Sam Lauber <sam124 at operamail dot com>, gcc at gcc dot gnu dot org
Date: Tue, 16 Nov 2004 09:40:55 -0800
Subject: Re: feature request
References: <20041116035745.6C11C23CE6@ws5-3.us4.outblaze.com> <419A3A57.4000902@nersc.gov>

On Tue, Nov 16, 2004 at 09:35:19AM -0800, David Skinner wrote:
> I was thinking more generally than just semicolons. Any single line 
> based syntax problem could report the context in the source in which the 
> error was encountered.

That would be really ugly for those of us that use gcc from an IDE
or with Emacs; the IDE or Emacs parses the file name and line number
and allows the programmer to step from one error to the next in a
window, where the context of the error is clear.

If you want to see the context of your errors, I suggest that you use
one of these solutions.

Follow-Ups:
- Re: feature request
  - From: Luca Benini

References:
- Re: feature request
  - From: Sam Lauber
- Re: feature request
  - From: David Skinner

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