Returns a path canonicalized for alphabetical comparison. - replaces "-" with "_" so they both cmp the same. - removes '-inl' since we don't

Report if too many lines in function body. Args: error: The function to call with any errors found. filename: The name of the current

Checks for improper use of DISALLOW* macros. Args: filename: The name of the current file. clean_lines: A CleansedLines instance containing

Check alternative keywords being used in boolean expressions. Args: filename: The name of the current file. clean_lines: A CleansedLines in

Run checks that applies to text up to the opening brace. This is mostly for checking the text after the class identifier and the "{", usually

Looks for misplaced braces (e.g. at the end of line). Args: filename: The name of the current file. clean_lines: A CleansedLines instance c

Checks the use of CHECK and EXPECT macros. Args: filename: The name of the current file. clean_lines: A CleansedLines instance containing t

Checks for common mistakes in TODO comments. Args: comment: The text of the comment from the line in question. filename: The name of the cu

Checks that all classes and namespaces have been completely parsed. Call this when all lines in a file have been processed. Args: filen

Look for empty loop/conditional body with only a single semicolon. Args: filename: The name of the current file. clean_lines: A CleansedLin

Run checks that applies to text after the closing brace. This is mostly used for checking end of namespace comments. Args: filename: T

Logs an error for each line containing bad characters. Two kinds of bad characters: 1. Unicode replacement characters: These indicate that eithe

Logs an error if no Copyright message appears at the top of the file.

Reports for long function bodies. For an overview why this is done, see: http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml#Write_Sho

Checks that the file contains a header guard. Logs an error if no #ifndef header guard is present. For other headers, checks that the full pathn

Reports for missing stl includes. This function will output warnings to make sure you are including the headers necessary for the stl containers

Logs an error if we see /* ... */ or "..." that extend past one line. /* ... */ comments are legit inside macros, for one line. Otherwise, we pre

Logs an error if there is no newline char at the end of the file. Args: filename: The name of the current file. lines: An array of strings,

Check for non-const references. Separate from CheckLanguage since it scans backwards from current line, instead of scanning forward. Args:

r"""Logs an error if we see certain non-ANSI constructs ignored by gcc-2. Complain about several constructs which gcc-2 accepts, but which are no

Check rules that are applicable to #include lines. Strings on #include lines are NOT removed from elided line, to make certain tasks easier. Howe

Checks for invalid increment *count++. For example following function: void increment_counter(int* count) { *count++; } is invalid, becau

Checks rules from the 'C++ language rules' section of cppguide.html. Some of these rules are hard to test (function overloading, using uint32 ina

Check that make_pair's template arguments are deduced. G++ 4.6 in C++0x mode fails badly if make_pair's template arguments are specified explicit

Returns a non-empty error message if the next header is out of order. This function also updates the internal state to be ready to check the

Checks for calls to thread-unsafe functions. Much code has been originally written without consideration of multi-threading. Also, engineers are

Checks for additional blank line issues related to sections. Currently the only thing checked here is blank line before protected/private. Args:

Checks for the correctness of various spacing issues in the code. Things we check for: spaces around operators, spaces after if/for/while/switch,

Checks for the correctness of various spacing around function calls. Args: filename: The name of the current file. line: The text of the li

Checks rules from the 'C++ style rules' section of cppguide.html. Most of these rules are hard to test (naming, comment style), but we do what we

Checks that VLOG() is only used for defining a logging level. For example, VLOG(2) is correct. VLOG(INFO), VLOG(WARNING), VLOG(ERROR), and VLOG(F

These routines together will solve an equation correctly */

Removes C++11 raw strings from lines. Before: static const char kData[] = R"( multi-line string )"; After: s

Copy constructor. */

Count line in current function body.

! \fn int DSDPAddLUBounds(DSDP dsdp,LUBounds lucone); \brief Set the constraints to the solver. \param lucone cone of bounds. \param dsdp the solver *

! \fn int DSDPAddSDP(DSDP dsdp, SDPCone sdpcone); \brief Pass a semidefinite cone to the solver. \param dsdp solver \param sdpcone semidefinite cone *

! \fn int DSDPBlockDataDestroy(DSDPBlockData *ADATA); \brief Free the data matrices \param ADATA block of data. */

! \fn int DSDPBlockFactorData(DSDPBlockData *ADATA, DSDPVMat X, SDPConeVec W){ \brief Factor the data matrices \param ADATA block of data. \param X w

! \fn int DSDPBlockInitialize(SDPblk *blk); \brief Initialize data structures in one block of the cone. \param blk block of semidefinite cone */