We also have similar issue as well, i.e extern
cregister volatile unsigned int
IFR; where cregister is a valid keyword for our compiler but there is an error
icon in the editor.
Is there anyway to contribute additional keywords
or is there other method to tell Coden to ignore such errors?
Thanks,
Patrick
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of James Blackburn
Sent: Friday, March 11, 2011 12:21
PM
To: CDT
General developers list.
Subject: Re: [cdt-dev] Codan
errors
There's this bug:
It's
currently not possible to distinguish between codan errors and compiler errors
which would be a nice feature to have.
On 11 March 2011 17:15, Schaefer, Doug <Doug.Schaefer@xxxxxxxxxxxxx>
wrote:
Hey gang,
In my daily usage
of Indigo, I often see Codan raising errors in my code even though it compiles
fine. This usually happens when I’m doing a complicated project and the
indexer hasn’t kept up with what I’m doing.
Of course false
errors will shake user’s confidence in the CDT. Should we be making these
warnings instead? Thoughts?
Thanks,
Doug.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev