mirror of
https://github.com/google/styleguide.git
synced 2024-03-22 13:11:43 +08:00
Style guides for Google-originated open-source projects
8190c132fd
- 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>.
Update Objective-C style guide to 2.52:
- Fix ARC example to not imply the use of @private in .m files.
- Add an example to the "Category Names" section.
- Require that ARC-using files insert preprocessor directives that
generate an error when compiling without ARC.
- Fix spacing around the *s in the ARC example per the C++ style
guide.
Update Python style guide to 2.48:
- Allow comments with URLs to exceed 80 characters per line.
- Update outdated implicit-line-joining URLs.
Update HTML/CSS style guide to 2.21:
- Consistent use of title case.
- Add new "Declaration Block Separation" section.
- Add a CSS example to the "Capitalization" section.
- Minor fixes to whitespace.
Update JavaScript style to guide to 2.72:
- Make it clear that the injunction against aliasing namespaces only
applies to local aliases, not goog.scope.
- Clarify the style guide's recommendation on array/object literals.
- Add documentation on @private {type}, @protected {type}, and
@const {type}.
- Make JSDoc descriptions required only if not obvious.
- Clarify that only private properties and methods need a trailing
underscore.
- Fix spelling of arv's name.
Update Common Lisp style guide to 1.18:
- Macro-defining macros are harder to understand for everyone, not
just for the "uninitiated." There's no need to condescend.
In all of the above style guides:
- The guide source is now encoded as UTF-8. The numeric character
references have been replaced with raw UTF-8-encoded characters.
|
||
|---|---|---|
| cpplint | ||
| cppguide.xml | ||
| eclipse-cpp-google-style.xml | ||
| eclipse-java-google-style.xml | ||
| google_python_style.vim | ||
| google-c-style.el | ||
| google-r-style.html | ||
| htmlcssguide.xml | ||
| intellij-java-google-style.xml | ||
| javascriptguide.xml | ||
| jsoncstyleguide_example_01.png | ||
| jsoncstyleguide_example_02.png | ||
| jsoncstyleguide.html | ||
| jsoncstyleguide.xml | ||
| lispguide.xml | ||
| objcguide.xml | ||
| pyguide.html | ||
| shell.xml | ||
| styleguide.css | ||
| styleguide.xsl | ||
| xmlstyle.html | ||
