google objective c编码规范

Google Objective-C Style Guide

Revision 2.36

Mike Pinkerton

Greg Miller

Dave MacLachlan

Each style point has a summary for which additional information is available by toggling the

accompanying arrow button that looks this way: ▽ . You may toggle all summaries with the big arrow

button:

Hooray! Now you know you can expand points to get more details. Alternatively, there's an

"expand all" at the top of this document.

Objective-C is a very dynamic, object-oriented extension of C. It's designed to be easy to use

The purpose of this document is to describe the Objective-C (and Objective-C++) coding

guidelines and practices that should be used for all Mac OS X code. Many of these guidelines

developed by Google conform to the requirements in this guide.

the Google Toolbox for Mac project (abbreviated GTM throughout this document). Code

meant to be shared across different projects is a good candidate to be included in this

Note that this guide is not an Objective-C tutorial. We assume that the reader is familiar with

the language. If you are new to Objective-C or need a refresher, please read The Objective-C

Unless an interface or implementation is very short, such as when declaring a handful of

private methods or a bridge class, adding blank lines usually helps readability.

Use only spaces, and indent 2 spaces at a time.

We use spaces for indentation. Do not use tabs in your code. You should set your editor to

but this should definitely be the exception and not commonplace.

If a reviewer asks that you reformat a line because they feel it can be fit in 80 columns and

still be readable, you should do so.

We recognize that this rule is controversial, but so much existing code already adheres to it,

Editing > Show page guide.

parameter list except between parameters.

When the first keyword is shorter than the others, indent the later lines by at least four spaces.

choice of formatting styles, follow the convention already used in a given source file.