- Add leading blank line exception.
- Improve guidance for function definition comments.
- Tweak class comment example to not violate type naming guidelines.
Update Objective-C style guide to 2.21:
- Prohibit +new.
Update JavaScript style guide to 2.9:
- Add new "Function Declarations Within Blocks" section.
- Add new "Internet Explorer's Conditional Comments" section.
- Add new "Alias long type names to improve readability" section.
- Add @lends.
- Allow overloading a function judiciously.
- _unittest and _regtest are deprecated.
- Document C++0x policy.
- Allow namespace aliases in .h files when inside namespaces.
- Give examples for and against parentheses with return.
- Update set of allowed Boost headers.
- Add a caveat to the forward-declaration section, mentioning impicit
constructors.
- Forbid the use of operator synonyms such as "and."
- Specify the naming convention (OrDie) to use when a function has
crash-on-failure semantics.
- Allow static const data members to be non-private.
- Specify placement of friend declarations.
- Require each file to include headers that they use.
Update Objective-C style guide to 2.18:
- Prefer @optional to informal protocols when possible.
- Specify formatting for invoking methods.
- Require that -dealloc be easy to review.
- Be explicit about "class Foo :\n public Bar" being wrong.
- Allow snprintf(NULL, 0, ...) pattern.
- Extend NOLINT syntax.
- Remove NOLINT hint.
- <new> is an STL header.
- Use original filename for header guard when invoked by flymake.
- Avoid false-positive build/include_what_you_use errors for use
of classes called "string" other than STL ones.
Review URL: http://codereview.chromium.org/1697023
- Add call_traits to the set of allowed boost libraries.
- Add an exception to the rule against default arguments to cover the useful
case of simulating variadic functions.
- Discourage the usage of ## in macros.
- Clarify example: it's acceptable to declare two parameters on one line even
if they don't all fit on that one line.
- Fix a typo ("make use symmetric spacing").
- Change bitwise AND to logical AND in a condition.
Update styleguide.xsl to 1.27:
- Change a bunch of SPANs into DIVs.
Update Python style guide to 2.15:
- Apply styleguide.xsl 1.27, changing a bunch of SPANs into DIVs.
- Make the messaging on DISALLOW_EVIL_CONSTRUCTORS more clear that we should
not be rewriting old code but should simply prefer DISALLOW_COPY_AND_ASSIGN
on new code.
- s/Initializer Lists/Constructor Initializer Lists/ since people search for
this based on knowing it's part of the constructor, but forget the precise
name.
- Allow data members in a test fixture to be private.
- Loosen restrictions on globals.
- Add explicit guideline for nested namespace formatting.
- Strengthen the prohibition against operator overloading for operator&.
- Add recommendation for "_" over "-" in file names.
- Revise the "Copy Constructors" section for brevity and clarity. Emphasize
preference for standard over nonstandard copy operations.
- Weaken the wording at the top of the "Doing Work in Constructors" section,
making it clear that Init() methods are not absolutely required for
non-trivial initialization.
- Fix minor typos and grammatical errors.
Update Objective-C style guide to 2.14:
- Add the Rule of Four for indenting parameters. Allow either of two forms
for formatting methods with short first keywords.
- Update the guidance on BOOL vs. bool.
- Whitespace cleanup.
Update Python style guide to 2.14:
- Consolidate discussion of the string module, apply, map, filter, and reduce
into a single section.
- Make it explicit that functions and classes can be nested inside methods.
- Optional check to make sure #includes are in alphabetical order.
- Optional "--counting=" option for statistics on what errors were found.
- Fix typos.
- Warn on overloading the unary operator&(). (Binary operator&() is fine).
- Fix false positives on "new int(x)"; it is not a cast.
- Allow "NOLINT" on header guards.
- Prevent members of a class from being "const string&".
- Don't check quoted filenames with irrelevant tests.
- Make cpplint accept 'for (foo; bar; ) {}'.
- Work with temporary files generated by Emacs flymake-mode.
- Don't warn on "/// Doxygen comments."
- Check the use of DCHECK in the same way we check the use of CHECK.
- Properly handle relative file paths with IncludeWhatYouUse checking.
- Start checking for IncludeWhatYouUse in a limited way in .cc files.
- Clarify that a "very strong convention" is, in fact, only very strong
within Google code
- Update the style guide with an additional naming possibility for enums:
kEnumName
- Reword the summary for the section on header file dependencies
- Simplify wording regarding static variables
Update Objective-C style guide to 2.11:
- Provide guidance on when to use #import and #include
- Display revision in style guide
Update styleguide.xsl with a hint of things to come
Set svn:eol-style on xmlstyle.html
- Prevent invalid increment constructs
- Allow long URLs in lines without hitting the 80 char limit
- Prevent false positives of "Extra space after ( in function call" in macro definitions.
- Allow comments with URLs to exceed the 80 column limit.
- Avoid false positives for "Lint failed to find start of function body"
test.
- Add checks for transform and min_element.
- Style fixes
Review URL: http://codereview.chromium.org/28056
- Allow unsigned types where defined overflow behavior is desired
- Clarify that a function-closing } is permitted on the same line as an
opening { for one-line functions
Set svn:eol-style = native on google-c-style.el