Syntax Error Anotations, but No Actual Errors

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Macgyver on Mon Jan 14 10:56:25 MST 2013
As I have been coding, I have progressed through several LPCXpresso updates (nowv5.0.14 build1109), and tried a few add-ins to help with Doxygen,Lint, etc. In one of my files I have several lines of codes that are flagged as syntax errors, but clearly are not and do not generate any compile errors or output in the console.

I have tried to locate settings for other installed modules/add-ins etc. to no avail. The problem is in a single file and in a single area consisting of around 200 lines of code with only a few function calls in between without error annotations on them. I have tried checking lines before/after/in between for errors, copying and pasting, etc, but the errors start and end in the same places. I have attached a screen shot of the section of code with error annotations (alothough it probably won't help).

Although this problem is mainly an annoyance, I would like to get it cleaned up as this problem has chased my code through several versions of LPCXpresso now.

Thanks in advance for the assistance.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Macgyver on Tue Jan 15 13:01:17 MST 2013
There are 0 unresolved includes resulting from a check via the indexer context menu in the project explorer window. I have checked the indexer setting properties and have not found any seetings that seem odd. I do not get any other warnings, indications, or anything else other than the annotations in the middle of a single .c file in my project, which consists of 49 .c and .h files that I have written, not including CMSIS or library include files.

O well. Just keep coding ;)

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Tue Jan 15 00:58:23 MST 2013
These errors are normally caused by the Indexer being unable to find/open all of the include files - suggest you look to see if there are any that it is unable to find.

Also, you have control over how the indexer and analyzer work by using the following preferences:
C/C++ - Indexer
C/C++ - Code Analysis

lpcware · ‎06-15-2016

Content originally posted in LPCWare by frame on Tue Jan 15 00:32:47 MST 2013

Quote:
Well, I suppose I will continue to ignore the annotations then. I guess I was just hoping there was a sticky Bit somewhere as the errors began on an 'else' statement.

It would be nice to get both in sync, yes.
But frankly, I don't know how, and I don't want to dig that deep into Eclipse (or NetBeans ...).
Hacking Eclipse is IMHO the task of the toolchain provider. Maybe the CodeRed support has an answer.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Macgyver on Mon Jan 14 12:43:14 MST 2013
Well, I suppose I will continue to ignore the annotations then. I guess I was just hoping there was a sticky Bit somewhere as the errors began on an 'else' statement.

O well, thanks for the help.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by frame on Mon Jan 14 12:16:05 MST 2013
Those "error annotations" come from the editor parser, not from the actual compiler, which is not involved at this point.
That is the downside of "syntax check while typing", if the parser and the compiler are not equally smart :(
I know this issue from several other Eclipse-based IDEs, and from NetBeans-based IDEs too.

It's annoying, but I (and colleagues of mine) have learnt to ignore it.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Macgyver on Mon Jan 14 11:12:43 MST 2013
I have rebuilt the indexer as specified, but errors persist. By the way, the errors show up in the editor for the file only. They are not flagged in the project explorer, nor are they indicated in any way by the console or problems tabs in the output.

Thanks.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Ex-Zero on Mon Jan 14 11:06:09 MST 2013
Didi you try a rebuild already?

Quote: CodeRedSupport
This might be an issue with the indexer getting out of sync. Try rebuilding the index by selecting the project showing up the warnings in the Project Explorer view, then right clicking and choosing [FONT=Courier New][SIZE=1]Index->Rebuild[/SIZE][/FONT] from the context sensitive menu.

Regards,
CodeRedSupport