openhub.net
Black Duck Software, Inc.
Open Hub
Follow @
OH
Sign In
Join Now
Projects
People
Organizations
Tools
Blog
BDSA
Projects
People
Projects
Organizations
C
cpplint/cpplint
Settings
|
Report Duplicate
0
I Use This!
×
Login Required
Log in to Open Hub
Remember Me
Low Activity
Commits
: Listings
Analyzed
2 days
ago. based on code collected
3 days
ago.
Jun 28, 2025 — Jun 28, 2026
Showing page 59 of 65
Search / Filter on:
Commit Message
Contributor
Files Modified
Lines Added
Lines Removed
Code Location
Date
Update google-c-style.el to #33. Review URL: https://codereview.appspot.com/8717044
[email protected]
More...
about 13 years ago
Update C++ style guide to 3.245: - Relax the rule for sizeof(varname) vs. sizeof(type). - Allow an exception for nonconst reference parameters where convention dictates their use, such as for swap. - C++11: allow static_assert. - Require non-trivial fall-through between cases in switch statements to be annotated. Trivial fall-through includes consecutive case labels with no intervening code, and no comment is required in these cases. - C++11: allow constexpr. - Revise the "Integer Types" section to note type-width problems. - Clarify that the "arguments on subsequent lines" function call style is acceptable even when the 80-column limit doesn't require it. - Boost: allow part of Polygon. - C++11: allow <tuple>.
[email protected]
More...
over 13 years ago
Update C++ style guide to 3.245: - Relax the rule for sizeof(varname) vs. sizeof(type). - Allow an exception for nonconst reference parameters where convention dictates their use, such as for swap. - C++11: allow static_assert. - Require non-trivial fall-through between cases in switch statements to be annotated. Trivial fall-through includes consecutive case labels with no intervening code, and no comment is required in these cases. - C++11: allow constexpr. - Revise the "Integer Types" section to note type-width problems. - Clarify that the "arguments on subsequent lines" function call style is acceptable even when the 80-column limit doesn't require it. - Boost: allow part of Polygon. - C++11: allow <tuple>.
[email protected]
More...
over 13 years ago
Initial public release of Shell Style Guide (1.25).
[email protected]
More...
over 13 years ago
Initial public release of Shell Style Guide (1.25).
[email protected]
More...
over 13 years ago
Updated cpplint.py to #224:
[email protected]
More...
over 13 years ago
Updated cpplint.py to #224:
[email protected]
More...
over 13 years ago
Google Common Lisp Style Guide, revision 1.17
[email protected]
More...
over 13 years ago
Google Common Lisp Style Guide, revision 1.17
[email protected]
More...
over 13 years ago
Update C++ style guide to 3.231: - Clarify that sentence-like non-sentence comments are permitted. - Note that older code with incorrect #include ordering should be fixed. - Revamp the section on default function arguments. - Avoid explicitly recommending Init() methods. - C++11: permit "auto". - C++11: permit ">>" in place of "> >". - C++11: permit range-based "for". - C++11: permit variadic macros (already permitted as a C++03 extension). - C++11: permit "LL" and "ULL" literal suffixes (already permitted as a C++03 extension). - Reflect the revised copyright and author line policy: copyright notices are not required, but license boilerplate may still be used (and generally contains a copyright notice). Author lines are not required. - C++11: permit new features in <algorithm> and the portion of <numeric> that does not require initializer lists. - Revise rules on forward declarations: explicitly forbid forward-declared functions, do not mandate forward declarations, discourage forward-declared templates. - Remove the rule requiring "const" qualifiers for member functions to be on the same line as the closing parenthesis of the parameter list. - Fix typo: "unnamed namespaces." - C++11: permit local types as template parameters. - Fix typo: "unfamiliar." - Relax RTTI rules to permit its use, but warn about its abuse. - C++11: permit nullptr and nullptr_t. Revise text referring to NULL to refer more generically to null pointers. - Remove the "don't go crazy with const" rule. - Fix typo: "dir/foo2" should bee "dir2/foo2." - Remove reference to a specific GCC version.
[email protected]
More...
over 13 years ago
Update C++ style guide to 3.231: - Clarify that sentence-like non-sentence comments are permitted. - Note that older code with incorrect #include ordering should be fixed. - Revamp the section on default function arguments. - Avoid explicitly recommending Init() methods. - C++11: permit "auto". - C++11: permit ">>" in place of "> >". - C++11: permit range-based "for". - C++11: permit variadic macros (already permitted as a C++03 extension). - C++11: permit "LL" and "ULL" literal suffixes (already permitted as a C++03 extension). - Reflect the revised copyright and author line policy: copyright notices are not required, but license boilerplate may still be used (and generally contains a copyright notice). Author lines are not required. - C++11: permit new features in <algorithm> and the portion of <numeric> that does not require initializer lists. - Revise rules on forward declarations: explicitly forbid forward-declared functions, do not mandate forward declarations, discourage forward-declared templates. - Remove the rule requiring "const" qualifiers for member functions to be on the same line as the closing parenthesis of the parameter list. - Fix typo: "unnamed namespaces." - C++11: permit local types as template parameters. - Fix typo: "unfamiliar." - Relax RTTI rules to permit its use, but warn about its abuse. - C++11: permit nullptr and nullptr_t. Revise text referring to NULL to refer more generically to null pointers. - Remove the "don't go crazy with const" rule. - Fix typo: "dir/foo2" should bee "dir2/foo2." - Remove reference to a specific GCC version.
[email protected]
More...
over 13 years ago
Google Common Lisp Style Guide, revision 1.16
[email protected]
More...
over 13 years ago
Google Common Lisp Style Guide, revision 1.16
[email protected]
More...
over 13 years ago
more extensions, and fix check
Thibault Kruse
More...
over 13 years ago
more extensions, and fix check
Thibault Kruse
More...
over 13 years ago
Google Common Lisp Style Guide, revision 1.15
[email protected]
More...
over 13 years ago
Google Common Lisp Style Guide, revision 1.15
[email protected]
More...
over 13 years ago
Google Common Lisp Style Guide updated to 1.13.
[email protected]
More...
over 13 years ago
Google Common Lisp Style Guide updated to 1.13.
[email protected]
More...
over 13 years ago
Google Common Lisp Style Guide, revision 1.12
[email protected]
More...
over 13 years ago
Google Common Lisp Style Guide, revision 1.12
[email protected]
More...
over 13 years ago
Google Common Lisp Style Guide updated to 1.11.
[email protected]
More...
over 13 years ago
Google Common Lisp Style Guide updated to 1.11.
[email protected]
More...
over 13 years ago
Google Common Lisp Style Guide updated to 1.10, integrating more feedback from inside and outside Google.
[email protected]
More...
over 13 years ago
Google Common Lisp Style Guide updated to 1.10, integrating more feedback from inside and outside Google.
[email protected]
More...
over 13 years ago
Manually add stylesheet information (for now) to lispguide.xml.
[email protected]
More...
over 13 years ago
Manually add stylesheet information (for now) to lispguide.xml.
[email protected]
More...
over 13 years ago
Publish the Google Common Lisp Style Guide, revision 1.8, for public review.
[email protected]
More...
over 13 years ago
Publish the Google Common Lisp Style Guide, revision 1.8, for public review.
[email protected]
More...
over 13 years ago
Updating python style guide
[email protected]
More...
almost 14 years ago
←
1
2
…
55
56
57
58
59
60
61
62
63
64
65
→
This site uses cookies to give you the best possible experience. By using the site, you consent to our use of cookies. For more information, please see our
Privacy Policy
Agree