Incremental file checking

[smogm NA]

A nice feature would be to have an optional possiblity to let vera++ create a database (XML file or anything) of already checked files, so that in a later run vera++ only checks files which had an error before or which are newer than their last scan. An "incremental file scan".

Currently I'm using a CMake workaround by creating "0 byte flag files" and parsing the produced checkstyle xml file to find out which files have to be checked in the next run.

Is it possible to implement such a feature?

[Gaëtan Lehmann]

We could add an extra output format that just list the files with style check problems. That file could then be reused to rerun vera++.

Something like:

vera++ --input files-to-check.txt --files-with-error-report files-to-check.txt

Note that files-to-check.txt must be recreated manually when all the errors have been fixed.

Would that work for you?

[smogm NA]

Gaëtan, this sounds nice!

it would also be nice if vera++ can recognize which files it has already checked and where not changed since the last check (like gnu make does with the compiler generated object files).

Do you think this is also possible?