Code Style. C/C++/Objective-C

Line breaks

If this option is selected, line breaks will be kept after reformatting the code. Otherwise, the lines that are shorter than a standard convention will be merged into one line.

Selected

Comment at first column

If this option is selected, comments placed at the first column won't change their position after reformatting the code. Otherwise, such comments will align with the next line of code.

Selected

Directive at first column

If this option is selected, directives placed at the first column won't change their position after reformatting the code. Otherwise, the directives will align with the surrounding code.

Selected

Control statement in one line

If this option is selected, control statements placed at the first column won't change their position after reformatting the code. Otherwise, the statements will align with the surrounding code.

Selected

Simple blocks and lambdas in one line

If this option is selected, simple single-line blocks and lambdas will be kept in one line after reformatting the code. Otherwise, they will expand into multiple lines.

Deselected

Simple methods and functions in one line

If this option is selected, simple methods and functions will be kept in line after reformatting the code. Otherwise, they will expand into multiple lines.

Deselected

Classes and structures in one line

If this option is selected, simple classes and structures will be kept in one line after reformatting the code. Otherwise, they will expand into multiple lines.

Deselected

Keep nested namespaces in one line

If this option is selected, nested namespaces will stay at the same line with the parent ones after reformatting the code. Otherwise, they will be moved to a new line.

Deselected

Wrapping style

From this list, select the desired wrapping style:

• Do not wrap: when this option is selected, no special wrapping style is applied.

  With this option selected, the nested alignment and braces settings are ignored.

• Wrap if long: select this option to have lines going beyond the right margin wrapped with proper indentation.

• Wrap always: select this option to have all elements in lists wrapped, so that there is one element per line with proper indentation.

• Chop down if long: select this option to have elements in lists that go beyond the right margin wrapped, so that there is one element per line with proper indentation.

Align when multiline

If this checkbox is selected, a code construct starts at the same column on each next line. Otherwise, the position of a code construct is determined by the current indentation level.

Align in columns

If this checkbox is selected, the variables names, types and initializers are aligned in columns, each variable on next line, as in example:

Before

After

<character(s)> on next line

Select this checkbox to have the specified character or characters moved to the next line when the lines are wrapped.

'else' on new line

Use this checkbox to have the corresponding statements or characters moved to the next line.

New line after <character>

Select this checkbox to have the code after the specified character moved to a new line.

Special else if treatment

If this checkbox is selected, else if statements are located in the same line.

Otherwise, else if statements are moved to the next line to the corresponding indent level.

Indent case branches

If this checkbox is selected, the case statement is located at the corresponding indent level. Otherwise, case statement is placed at the same indent level with switch.

Braces placement style

Use this list to specify the position of the opening brace in class declarations, method declarations, and other types of declarations. The available options are:

• End of line: select this option to have the opening brace placed at the declaration line end.

• Next line if wrapped: select this option to have the opening brace placed at the beginning of the line after the multiline declaration line.

• Next line: select this option to have the opening brace placed at the beginning of the line after the declaration line.

• Next line shifted: select this option to have the opening brace placed at the line after the declaration line being shifted to the corresponding indent level.

• Next line, each shifted: select this option to have the opening brace placed at the line after the declaration line being shifted to the corresponding indent level, and have the next line shifted to the next indent level as well.

Force braces

From this list, choose the braces introduction method for if, for, while, and do () while statements. The available options are:

• Do not force: select this option to suppress introducing braces automatically.

• When multiline: select this option to have braces introduced automatically if a statement occupies more than one line. Note that AppCode analyzes the number of lines in the entire statement but not only its condition.

  For example, if the code is

  int foo (int Days) { if ((Days % 10) == 3) return 1; else return 0; }

  AppCode will insert braces automatically:

  int foo (int Days) { if ((Days % 10) == 3) { return 1; } else { return 0; } }

• Always: select this checkbox to have braces always introduced automatically.

Line comment at first column

Select this checkbox to have generated line comments placed in the first column.

Add a space at comment start

Select this checkbox to have a space placed after // in generated line comments. This option is available only if the Line comment at first column checkbox is cleared.

Block comment at first column

Select this checkbox to have generated block comments placed in the first column.

Prefix for instance variables

Suffix for instance variables

In these text boxes, type the prefixes and suffixes to be used when generating instance variables.

Retain object parameters in initWith...

Select this checkbox to retain object parameters when generating initWith. This option will not work unless Automated Reference Counting is disabled.

Use property setters in initWith...

Select this checkbox to use property setters when generating initWith. This option will not work unless instant variable has a synthesized property.

Semicolon after method signature in implementation

Select this checkbox to insert a semicolon after method signature when generating method implementation.

Put ivars to implementation if possible

Select this checkbox to insert instant variables where possible when generating implementation.

Use NSInteger and CGFloat in introduce variable

Select this checkbox to use NSInteger and CGFloat in introduce variable. Otherwise int and float will be used.

Ivars release style (for 'dealloc')

Choose instant variables release style for dealloc method. The available options are:

• [ivar release]

• [ivar release], ivar=nill

• property=nill

Generate ivar declarations for properties

Choose the behaviour for generating instant variable declarations for properties. The available options are:

• Always generate

• Never generate

• Ask

Prefix for fields

Type the prefix that will prepend a name of an automatically generated field.

Suffix for fields

Type the suffix that will be appended to a name of an automatically generated field.

Prefix for getters

Type a prefix that will prepend a name of an automatically generated getter. The default name is get

Prefix for setters

type a prefix that will prepend a name of an automatically generated setter. The default name is set

Generate != together with ==

select this checkbox to enable this setting as default for Select Fields dialog when generating an equality operator.

Generate >,<=,>= together with <

select this checkbox to enable this setting as default for Select Fields dialog when generation a relational operator.

Add @brief tag

Select this checkbox to enable the @brief tag in Doxygen style comments.

Tag prefix in line comments

Click @param or \param option to select the preferred prefix type.

Tag prefix in block comments

Click @param or \param option to select the preferred prefix type.