David RodrÃguez Ibeas wrote:
On 10/10/07, John Femiani <JOHN.FEMIANI@asu.edu> wrote:
aligned_storage.hpp:160: [L001] trailing whitespace -fix1: vera++ -transform trim_right aligned_storage.hpp -fix2: vera++ -transform som_other_transform aligned_storage.hpp
I would consider that more like a plugin for whichever IDE you are using
Yes. The next release of Vera++ will be able to include the rule number in the report line if some command-line option is given. This will be very easy to parse/extract and then linked with any behaviour needed. Note also that it is typical for a single rule to trigger *many* times on a larger body of code. It would not be very comfortable to get these hints repeated thousand times.
//@ignore_rule L001
I agree on this with some previous post: I don't think that is a good option
Similarly, Vera++ will support lists of exclusions, which will be provided *externally*. There is no need to be intrusive in the code itself to achieve this. Note also that proper implementation of exclusion lists will allow to handle whole groups of files - for example all files from specific directory (this actually makes sense in Boost, especially for files that are test cases for wave - they intentionally break all possible rules). It would be inefficient to impose comments like above into such files, especially if it could interfere with the parser test case that a given file is supposed to implement. Regards, -- Maciej Sobczak * www.msobczak.com * www.inspirel.com