Displaying 3 results from an estimated 3 matches for "include_order".
2012 Jun 05
3
[LLVMdev] sample of running google c++ lint script
...Copyright [year] <Copyright Owner>" [legal/copyright] [5]
Target.cpp:10: Line ends in whitespace. Consider deleting these extra
spaces. [whitespace/end_of_line] [4]
Target.cpp:22: Found C++ system header after other header. Should be:
Target.h, c system, c++ system, other. [build/include_order] [4]
Target.cpp:24: Do not use namespace using-directives. Use
using-declarations instead. [build/namespaces] [5]
Target.cpp:26: Is this a non-const reference? If so, make const or use
a pointer. [runtime/references] [2]
Target.cpp:65: Use int16/int64/etc, rather than the C type long
[run...
2012 Jun 05
0
[LLVMdev] sample of running google c++ lint script
...t; spaces. [whitespace/end_of_line] [4]
We have an incredible amount of those, and fixing them would create far
too much churn. I generally fix them on the code I touch.
> Target.cpp:22: Found C++ system header after other header. Should be:
> Target.h, c system, c++ system, other. [build/include_order] [4]
The LLVM convention is to reverse the "usual" order. The first file any
.cpp includes should be its own .h. Then other project headers. Then, in
the case of Clang, the LLVM headers. And finally system and standard
headers.
> Target.cpp:24: Do not use namespace using-directives...
2012 Jun 05
4
[LLVMdev] sample of running google c++ lint script
...espace/end_of_line] [4]
> We have an incredible amount of those, and fixing them would create far
> too much churn. I generally fix them on the code I touch.
>> Target.cpp:22: Found C++ system header after other header. Should be:
>> Target.h, c system, c++ system, other. [build/include_order] [4]
> The LLVM convention is to reverse the "usual" order. The first file any
> .cpp includes should be its own .h. Then other project headers. Then, in
> the case of Clang, the LLVM headers. And finally system and standard
> headers.
>> Target.cpp:24: Do not use names...