@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.)
hq.recaptime.dev/wiki/Phorge
phorge
phabricator
Don't say "K&R style" in coding conventions
Summary: We technically don't use K&R. These documents and the rest of the codebase are full of examples of the correct style, which should be unambiguous to a reasonable reader.
Test Plan: reading
Reviewers: staticshock, btrahan
Reviewed By: btrahan
Subscribers: epriestley
Differential Revision: https://secure.phabricator.com/D11255
-2
-1
src/docs/contributor/javascript_coding_standards.diviner
-1
src/docs/contributor/javascript_coding_standards.diviner
···
18
18
19
19
- Use two spaces for indentation. Don't use literal tab characters.
20
20
- Use Unix linebreaks ("\n"), not MSDOS ("\r\n") or OS9 ("\r").
21
-
- Use K&R style braces and spacing.
22
21
- Put a space after control keywords like ##if## and ##for##.
23
22
- Put a space after commas in argument lists.
24
23
- Put space around operators like ##=##, ##<##, etc.
-1
src/docs/contributor/php_coding_standards.diviner
-1
src/docs/contributor/php_coding_standards.diviner
···
19
19
20
20
- Use two spaces for indentation. Don't use tab literal characters.
21
21
- Use Unix linebreaks ("\n"), not MSDOS ("\r\n") or OS9 ("\r").
22
-
- Use K&R style braces and spacing.
23
22
- Put a space after control keywords like ##if## and ##for##.
24
23
- Put a space after commas in argument lists.
25
24
- Put a space around operators like ##=##, ##<##, etc.