File: google-objc-function-naming.rst

package info (click to toggle)
llvm-toolchain-11 1%3A11.0.1-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 995,808 kB
  • sloc: cpp: 4,767,656; ansic: 760,916; asm: 477,436; python: 170,940; objc: 69,804; lisp: 29,914; sh: 23,855; f90: 18,173; pascal: 7,551; perl: 7,471; ml: 5,603; awk: 3,489; makefile: 2,573; xml: 915; cs: 573; fortran: 503; javascript: 452
file content (27 lines) | stat: -rw-r--r-- 839 bytes parent folder | download | duplicates (31) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
 
.. title:: clang-tidy - google-objc-function-naming

google-objc-function-naming
===========================

Finds function declarations in Objective-C files that do not follow the pattern
described in the Google Objective-C Style Guide.

The corresponding style guide rule can be found here:
https://google.github.io/styleguide/objcguide.html#function-names

All function names should be in Pascal case. Functions whose storage class is
not static should have an appropriate prefix.

The following code sample does not follow this pattern:

.. code-block:: objc

  static bool is_positive(int i) { return i > 0; }
  bool IsNegative(int i) { return i < 0; }

The sample above might be corrected to the following code:

.. code-block:: objc

  static bool IsPositive(int i) { return i > 0; }
  bool *ABCIsNegative(int i) { return i < 0; }