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
Unknown Object (File)
Wed, Dec 11, 3:01 AM
Unknown Object (File)
Fri, Dec 6, 5:09 AM
Unknown Object (File)
Wed, Dec 4, 4:57 AM
Unknown Object (File)
Wed, Nov 27, 5:26 AM
Unknown Object (File)
Mon, Nov 25, 12:52 AM
Unknown Object (File)
Sat, Nov 23, 5:29 PM
Unknown Object (File)
Thu, Nov 21, 12:38 PM
Unknown Object (File)
Nov 17 2024, 11:13 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.