Page MenuHomePhabricator

Don't say "K&R style" in coding conventions
ClosedPublic

Authored by epriestley on Jan 6 2015, 6:40 PM.
Tags
None
Referenced Files
F15418909: D11255.id27015.diff
Fri, Mar 21, 2:19 AM
F15381728: D11255.diff
Fri, Mar 14, 9:05 AM
F15302862: D11255.diff
Wed, Mar 5, 11:04 PM
Unknown Object (File)
Feb 9 2025, 9:55 AM
Unknown Object (File)
Feb 8 2025, 12:54 AM
Unknown Object (File)
Feb 8 2025, 12:54 AM
Unknown Object (File)
Feb 8 2025, 12:54 AM
Unknown Object (File)
Feb 8 2025, 12:54 AM
Subscribers

Details

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

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Don't say "K&R style" in coding conventions.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added reviewers: staticshock, btrahan.
btrahan edited edge metadata.
This revision is now accepted and ready to land.Jan 6 2015, 6:46 PM
This revision was automatically updated to reflect the committed changes.