Community
Participate
Working Groups
CDT HEAD: Codan problem markers are created when a file is opened in an editor, but are not removed when the editor is closed. This may cause markers in the Problems view to become stale if changes made to other files eliminate the cause of the problem.
This is intended behavior - codan markers are persistent. Your statement is true for all persistent markers - if file changes outside of eclipse they become obsolete. Even if they are not persistent - if you change file in vi outside of eclipse nothing we can do about it.
(In reply to comment #1) The inconsistency happens during normal editing in Eclipse. Consider the following scenario: test.h ------ struct A { int x; }; test.cc ------- #include "test.h" B b; 1. User opens test.cc and gets a problem marker on test.cc line 2. 2. User closes test.cc. 3. User opens test.h changes A to B and saves the file. The marker on test.cc line 2 persists in spite of the name resolution problem being fixed.
There are problems that are generated on demand and some that are not (for example some complex dead lock problem which is very computationally expensive). So for the first case we can re-run checkers when file is open.
It makes sense to have some symmetry. The problem markers generated by the checkers that run only when a file is open in an editor should be erased when the file is closed. The markers created by other checkers should stay.
that sounds good
