This is the mail archive of the gcc-patches@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: implement fdiagnostics-print-source-range-info



On Aug 4, 2009, at 9:28 AM, Manuel López-Ibáñez wrote:


2009/8/4 Chris Lattner <clattner@apple.com>:


Sounds great, thanks Manuel. FWIW, one subtle thing that
-fdiagnostics-print-source-range-info-gnu does is it causes the caret
diagnostics to be indented by an extra space. This means that an IDE just

You mean that this is not done always that caret info is printed? In my prototype of caret info, it was always indented by an extra space.

Ok, that works too. We only do this with -fdiagnostics-print-source- range-info.


I don't know if this is interesting to the GCS or not.

In any case, -fdiagnostics-print-source-range-info does not enable caret diagnostics, it just enables printing the extra range numbers. GCC does not have caret diagnostics yet.

Right, you can also use -fno-caret-diagnostics to turn them off. For our purposes, it was nice for the textual caret to show up in the "build log" that the IDE displays. I agree the source-range-info is orthogonal from printing the caret and ranges "prettily".


-Chris


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