Index of available Vera++ rules

F001 Source files should not use the '\r' (CR) character
F002 File names should be well-formed
L001 No trailing whitespace
L002 Don't use tab characters
L003 No leading and no trailing empty lines
L004 Line cannot be too long
L005 There should not be too many consecutive empty lines
L006 Source file should not be too long
T001 One-line comments should not have forced continuation
T002 Reserved names should not be used for preprocessor macros
T003 Some keywords should be followed by a single space
T004 Some keywords should be immediately followed by a colon
T005 Keywords break and continue should be immediately followed by a semicolon
T006 Keywords return and throw should be immediately followed by a semicolon or a single space
T007 Semicolons should not be isolated by spaces or comments from the rest of the code
T008 Keywords catch, for, if, switch and while should be followed by a single space
T009 Comma should not be preceded by whitespace, but should be followed by one
T010 Identifiers should not be composed of 'l' and 'O' characters only
T011 Curly brackets from the same pair should be either in the same line or in the same column
T012 Negation operator should not be used in its short form
T013 Source files should contain the copyright notice
T014 Source files should refer the Boost Software License
T015 HTML links in comments and string literals should be correct
T016 Calls to min/max should be protected against accidental macro substitution
T017 Unnamed namespaces are not allowed in header files
T018 Using namespace is not allowed in header files
T019 Control structures should have complete curly-braced block of code