| commit | b726be15885d9e7506d00a26d5450e7948ce016a | [log] [tgz] |
|---|---|---|
| author | Tony Ruscoe <tonyruscoe@gmail.com> | Fri Feb 24 14:43:16 2017 +0000 |
| committer | GitHub <noreply@github.com> | Fri Feb 24 14:43:16 2017 +0000 |
| tree | a1abd50148388400d5b2571ddcd322cbdcbcc040 | |
| parent | d0960a41c0d6d06942c54ba294b831bc77eef960 [diff] | |
| parent | a1773f9b3b69742d8952a63197afa0e8d72257a1 [diff] |
Merge pull request #233 from tonyruscoe/gh-pages-anchor-and-emphasis Add an anchor for the “Parting Words” section and change the emphasis on “Be consistent.”
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 holds 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.
Our 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 are now available. We have also released 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, our 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.
These style guides 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.
