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: [RFC] GCC caret diagnostics

From: "Gabriel Dos Reis" <gdr at integrable-solutions dot net>
To: "Andi Kleen" <andi at firstfloor dot org>
Cc: "Ian Lance Taylor" <iant at google dot com>, tromey at redhat dot com, "Manuel López-Ibáñez" <lopezibanez at gmail dot com>, "GCC Mailing List" <gcc at gcc dot gnu dot org>
Date: Fri, 14 Mar 2008 17:40:04 -0500
Subject: Re: [RFC] GCC caret diagnostics
References: <6c33472e0803021226o7d30c1b5rb811db0591cb4086@mail.gmail.com> <m3r6em4jij.fsf@fleche.redhat.com> <m3fxv2ezpo.fsf@google.com> <87r6ele0vb.fsf@basil.nowhere.org>

On 08 Mar 2008 15:39:20 +0100, Andi Kleen <andi@firstfloor.org> wrote:
> Ian Lance Taylor <iant@google.com> writes:
>
>  >Another approach would be to only use the carets for parse errors,
>  >which is where they are the most helpful.
>
>  And preprocessor if possible

Yes, definitely.

References:
- [RFC] GCC caret diagnostics
  - From: Manuel López-Ibáñez
- Re: [RFC] GCC caret diagnostics
  - From: Tom Tromey
- Re: [RFC] GCC caret diagnostics
  - From: Ian Lance Taylor
- Re: [RFC] GCC caret diagnostics
  - From: Andi Kleen

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