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: Better GCC diagnostics

From: Chris Lattner <clattner at apple dot com>
To: Manuel López-Ibáñez <lopezibanez at gmail dot com>
Cc: GCC Development <gcc at gcc dot gnu dot org>, Aldy Hernandez <aldyh at redhat dot com>, Tom Tromey <tromey at redhat dot com>, Gabriel Dos Reis <gdr at integrable-solutions dot net>, "Joseph S. Myers" <joseph at codesourcery dot com>
Date: Fri, 15 Aug 2008 08:32:39 -0700
Subject: Re: Better GCC diagnostics
References: <6c33472e0808150709u9420a23s6391cbc669c8c562@mail.gmail.com>

D) Printing Ranges. This requires:

*) Printing accurate column information. Similar to (B) above.
  *) A location(s) -> source strings interface and machinery. Similar
     to (A.3) above.

Ranges also require some way to get the end of a token (in addition to its beginning). For example, a range for:

X + some_long\
_ident??/
ifier

The range should start at "X" and end at "r". This is just a location like any other, but requires passing down like the begin loc. You might instead decide to do some fuzzy matching or something, but clang at least gets this right. This is important for other clients of the loc info, e.g. refactoring clients.

-Chris

Follow-Ups:
- Re: Better GCC diagnostics
  - From: Manuel López-Ibáñez

References:
- Better GCC diagnostics
  - From: Manuel López-Ibáñez

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