Community
Participate
Working Groups
The UI keeps reporting the line having issues, even after correcting the same. E.g.: If there is an compilation error (compiled using makefile - weird requirement for CDT to work), When the file is opened in CDT it shows the line having compilation error with red colored "X" and with red underline. It remains there even though that error is corrected and the file is saved (with same error message displayed), keeping user in dilemma whether the change is right or wrong...This is not true with the JAVA version, where it removes the error identifier/message... Also the auto correction is more matured with JAVA version; but CDT is lot behind in that...at-least it should work for type casting which is very critical in C++. I can see the error showing type mismatch but CDT doesn't do any auto-correction.
not a parser issue, the markers of the build-output parser sometimes don't disappear.
Note that errors and warnings reported from the compiler are only removed when the file is compiled again. You cannot expect them to be removed when just saving the file. BTW, this is basically the same with JDT. If automatic build is disabled JDT behaves similar.
Thats not true; i use JDT heavily with automatic build turned-off (reason i use the build script that is easier for me to invoke)....I can see the error message disappearing and in case if the code change is wrong, the auto correction listing the new suggestion....I don't have to compile the java files to see that...
Why is it P3, as i know this (these kind of) feature in java-eclipse made it popular...To make the CDT popular, this smaller issues needs to be addressed first.
