Home | History | Annotate | Download | only in tools

Lines Matching full:lint

32 # that I think are possible to flag automatically in a lint tool.  If these were
33 # caught by lint, it would save time both for myself and that of my reviewers.
34 # Most likely, some of these are beyond the scope of the current lint framework,
65 """Does google-lint on c++ files.
860 """Logs the fact we've found a lint error.
1263 in this lint program, so we warn about both.
1280 'Lint may give bogus warnings. '
1287 'Multi-line string ("...") found. This lint script doesn\'t '
1550 to #endif. We still perform lint checks on these lines, but
1762 not standard C++. Warning about these in lint is one way to ease the
1962 of vertical space and comments just to get through a lint check.
2011 'Lint failed to find start of function body.')
3208 # out for loops, which lint otherwise mistakenly thinks are functions.
3826 """Performs lint checks and reports any errors to the given error function.
3870 """Does google-lint on a single file.
3968 The list of filenames to lint.