styleguide/objective-c/objective-c.md - Issue 2712863004: [Documentation] Fix markdown in ObjC styleguide.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: styleguide/objective-c/objective-c.md

Issue 2712863004: [Documentation] Fix markdown in ObjC styleguide. (Closed)

Patch Set: Created 3 years, 9 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

« no previous file with comments | « no previous file | no next file » | no next file with comments »

OLD	NEW
1 # Chromium Objective-C and Objective-C++ style guide	1 # Chromium Objective-C and Objective-C++ style guide

2	2

3 _For other languages, please see the [Chromium style guides](https://chromium.go oglesource.com/chromium/src/+/master/styleguide/styleguide.md)._	3 _For other languages, please see the [Chromium style guides](https://chromium.go oglesource.com/chromium/src/+/master/styleguide/styleguide.md)._

4	4

5 Chromium follows the [Google Objective-C style guide]	5 Chromium follows the

6 (https://google.github.io/styleguide/objcguide.xml) unless an exception	6 [Google Objective-C style guide](https://google.github.io/styleguide/objcguide.x ml)

7 is listed below.	7 unless an exception is listed below.

8	8

9 A checkout should give you	9 A checkout should give you

10 [clang-format](https://chromium.googlesource.com/chromium/src/+/master/docs/clan g_format.md)	10 [clang-format](https://chromium.googlesource.com/chromium/src/+/master/docs/clan g_format.md)

11 to automatically format Objective-C and Objective-C++ code. By policy, Clang's	11 to automatically format Objective-C and Objective-C++ code. By policy, Clang's

12 formatting of code should always be accepted in code reviews. If Clang's	12 formatting of code should always be accepted in code reviews. If Clang's

13 formatting doesn't follow this style guide, file a bug.	13 formatting doesn't follow this style guide, file a bug.

14	14

15 ## Line length	15 ## Line length

16	16

17 For consistency with the 80 character line length used in Chromium C++ code,	17 For consistency with the 80 character line length used in Chromium C++ code,

(...skipping 21 matching lines...) Expand all Loading...
39 For code in an `@implementation` block, use the Objective-C naming rules. For	39 For code in an `@implementation` block, use the Objective-C naming rules. For

40 code in a method of a C++ class, use the C++ naming rules.	40 code in a method of a C++ class, use the C++ naming rules.

41	41

42 For C functions and constants defined in a namespace, use C++ style, even if	42 For C functions and constants defined in a namespace, use C++ style, even if

43 most of the file is Objective-C.	43 most of the file is Objective-C.

44	44

45 `TEST` and `TEST_F` macros expand to C++ methods, so even if a unit test is	45 `TEST` and `TEST_F` macros expand to C++ methods, so even if a unit test is

46 mostly testing Objective-C objects and methods, the test should be written using	46 mostly testing Objective-C objects and methods, the test should be written using

47 C++ style.	47 C++ style.

48	48

OLD	NEW