Cpplint is an open source tool used to check source code against the Google C++ Style Guide. The code is run from the command line as shown below, and results in output similar to that shown<\/p>\n\n\n\n
$ cpplint file1.cpp\nfile.cpp:1: Include the directory when naming .h files [build\/include_subdir] [4]\nfile.cpp:2: Include the directory when naming .h files [build\/include_subdir] [4]\nfile.cpp:88: Use int16\/int64\/etc, rather than the C type long [runtime\/int] [4]\nfile.cpp:89: Use int16\/int64\/etc, rather than the C type long [runtime\/int] [4]<\/pre>\n\n\n\nThe style guide suggests that all header files should be listed relative to the projects source directory without use of unix aliases such as
.<\/code> (current directory) or..<\/code> (parent directory). As such, the format for an include of a file located atproject\/src\/base\/file.h<\/code> would look like<\/p>\n\n\n\n#include \"base\/file.h\"<\/pre>\n\n\n\nWhere integer types are concerned the guide suggests that the only built-in integer type that should be used is
int<\/code>, and that all other required types should be taken from<stdint.h><\/code> implying that short should be replaced withint16_t<\/code> andlong long<\/code> withint64_t<\/code>. The standard also suggests that the use of unsigned types should be avoided unless they are specifically required.<\/p>\n\n\n\nSupposing that you don’t want to modify your code to remove these warning messages. One solution is to call cpplint using filters as shown below:<\/p>\n\n\n\n
$ cpplint --filter=-build\/include_subdir --filter=-runtime\/int file1.cpp<\/pre>\n\n\n\n<\/p>\n","protected":false},"excerpt":{"rendered":"
Cpplint is an open source tool used to check source code against the Google C++ Style Guide. The code is run from the command line as shown below, and results in output similar to that shown $ cpplint file1.cpp file.cpp:1: Include the directory when naming .h files [build\/include_subdir] [4] file.cpp:2: Include the directory when naming … <\/p>\n