see, for example, bug 108720
It contains a simple example that demonstrates how gcc error
annotations are flagged as errors and how the problems view reorders
entries based on severity, resource and line number in a manner that
confuses many users. Although the problems view allows for reordering
of entries, it is often impossible to match the order in the build
console.
Working with the developers of the tool chain (i.e. gcc team) to
produce machine-readable errors consistently is the only way to really
solve this problem, IMHO.
Recoskie, Chris wrote:
Note that a
correct parse might be
dependent on your toolchain properly reporting what macros the compiler
defines, if you have conditionally compiled code.
Also, I find
that the parser predictably
falls down on our own TI-specific compiler intrinsics. I can’t really
define them as macros, and there’s no way that I know of short of
messing
directly with the parser to get the parser to understand these. Right
now we
just sort of live with these being detected as errors. It would be
nice in the
future to be able to specify these via some sort of extension point. I
ought
to file this in Bugzilla but haven’t gotten around to it yet (along
with
10,000 other things…).
___________________________________________
Chris
Recoskie
The
parser that fills the
outline view is pretty generic and should be able to handle aCC. A bug
report
with some sample code that can reproduce the error would be helpful so
we can
debug the parser and see what’s going on.
Cheers,
Doug
Hi Doug,
Is 'gcc' format being used to parse these files? For HP-UX, we are
using
'aCC' for compiling the files. The compilation does not produce any
error. But,
the editor shows these 'syntax' errors.
I will file a bug with all the information discussed here.
Thanks,
sumit
On 10/21/05, Doug
Schaefer <DSchaefer@xxxxxxx>
wrote:
There is a little advertised
feature of the parse that
populates the outline
view. If it thinks it detects a syntax error, it will underline it in
red.
If it is incorrectly doing so with some code you have, please file a
bug
report with sample code to reproduce it.
Thanks,
Doug
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:
cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Ploett, Norbert
> Sent: Friday, October 21, 2005 2:22 AM
> To: CDT General developers list.
> Subject: AW: [cdt-dev] Error in Editor & so does not appear in
the
Outline
> view.
>
> Hi Bala,
>
> looks strange. I never saw underlined text without any markers and
> corresponding messages in the Problems view.
> Did you look into the Problems view? (Window --> Show View
-->
Problems)
> Do you get any hover information when hovering over the underlined
text?
>
>
> Norbert
>
> -----Ursprüngliche Nachricht-----
> Von: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx]
Im
> Auftrag von Balasubramaniyan K
> Gesendet: Freitag, 21. Oktober 2005 08:09
> An: cdt-dev@xxxxxxxxxxx
> Betreff: [cdt-dev] Error in Editor & so does not appear in the
Outline
> view.
>
>
> Hi
>
> I created a project & am editing
the project. But I see some red
> lines on some of my functions as shown in the attached
> image.
> I think the editor does not understand
some format. Should we make
> the editor understand all the formats ? ofCourse we can
> disable the red lines by unchecking the Hover
>
> Moreover if the function has some
error then they do not appear on
> the Outline view.
>
> Thanks,.\
> Bala
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
--
Matthias Spycher, Principal Engineer, CoWare, Inc.
tel:+1(408)392-8596, fax:+1(408)346-4740, http://www.coware.com
|