Android: Add repository import files am: b397128e82 am: 333e3bc131
am: 17eb825388

Change-Id: I2fd899fcb7d54faa11924065f466ed1f0e5550a0
tree: 5bb51bf6c3d96228f092e6d01f5ccfd73be7bb77
  1. LICENSE
  2. METADATA
  3. MODULE_LICENSE_BSD
  4. MODULE_LICENSE_CC
  5. NOTICE
  6. OWNERS
  7. README.md
  8. Rguide.xml
  9. angularjs-google-style.html
  10. cppguide.html
  11. cppguide.xml
  12. cpplint/
  13. docguide/
  14. eclipse-cpp-google-style.xml
  15. eclipse-java-google-style.xml
  16. google-c-style.el
  17. google-r-style.html
  18. google_python_style.vim
  19. htmlcssguide.html
  20. htmlcssguide.xml
  21. include/
  22. intellij-java-google-style.xml
  23. javaguide.css
  24. javaguide.html
  25. javaguidelink.png
  26. javascriptguide.xml
  27. jsguide.html
  28. jsoncstyleguide.html
  29. jsoncstyleguide.xml
  30. jsoncstyleguide_example_01.png
  31. jsoncstyleguide_example_02.png
  32. lispguide.xml
  33. objcguide.md
  34. objcguide.xml
  35. pyguide.html
  36. shell.xml
  37. styleguide.css
  38. styleguide.xsl
  39. vimscriptfull.xml
  40. vimscriptguide.xml
  41. xmlstyle.html
README.md

Google Style Guides

Every major open-source project has its own style guide: a set of conventions (sometimes arbitrary) about how to write code for that project. It is much easier to understand a large codebase when all the code in it is in a consistent style.

“Style” covers a lot of ground, from “use camelCase for variable names” to “never use global variables” to “never use exceptions.” This project (google/styleguide) links to the style guidelines we use for Google code. If you are modifying a project that originated at Google, you may be pointed to this page to see the style guides that apply to that project.

This project holds the C++ Style Guide, Objective-C Style Guide, Java Style Guide, Python Style Guide, R Style Guide, Shell Style Guide, HTML/CSS Style Guide, JavaScript Style Guide, AngularJS Style Guide, Common Lisp Style Guide, and Vimscript Style Guide. This project also contains cpplint, a tool to assist with style guide compliance, and google-c-style.el, an Emacs settings file for Google style.

If your project requires that you create a new XML document format, the XML Document Format Style Guide may be helpful. In addition to actual style rules, it also contains advice on designing your own vs. adapting an existing format, on XML instance document formatting, and on elements vs. attributes.

The style guides in this project are licensed under the CC-By 3.0 License, which encourages you to share these documents. See https://creativecommons.org/licenses/by/3.0/ for more details.

The following Google style guides live outside of this project: Go Code Review Comments and Effective Dart.