- 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
- Change list of permitted Boost libraries
- Permit one space before // in a new {scope}
- Grammar fix!
Update Objective-C style guide:
- Link spacing changes only
