File: google-objc-avoid-throwing-exception.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 (39 lines) | stat: -rw-r--r-- 1,018 bytes parent folder | download | duplicates (7) 
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
28
29
30
31
32
33
34
35
36
37
38
39
 
.. title:: clang-tidy - google-objc-avoid-throwing-exception

google-objc-avoid-throwing-exception
====================================

Finds uses of throwing exceptions usages in Objective-C files.

For the same reason as the Google C++ style guide, we prefer not throwing 
exceptions from Objective-C code.

The corresponding C++ style guide rule:
https://google.github.io/styleguide/cppguide.html#Exceptions

Instead, prefer passing in ``NSError **`` and return ``BOOL`` to indicate success or failure.

A counterexample:

.. code-block:: objc

  - (void)readFile {
    if ([self isError]) {
      @throw [NSException exceptionWithName:...];
    }
  }

Instead, returning an error via ``NSError **`` is preferred:

.. code-block:: objc

  - (BOOL)readFileWithError:(NSError **)error {
    if ([self isError]) {
      *error = [NSError errorWithDomain:...];
      return NO;
    }
    return YES;
  }

The corresponding style guide rule:
https://google.github.io/styleguide/objcguide.html#avoid-throwing-exceptions