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
F14058355: D11255.diff
Sun, Nov 17, 11:13 AM
F14031919: D11255.id27014.diff
Sat, Nov 9, 12:16 PM
Unknown Object (File)
Oct 18 2024, 5:45 AM
Unknown Object (File)
Oct 4 2024, 6:31 PM
Unknown Object (File)
Sep 15 2024, 3:50 PM
Unknown Object (File)
Sep 4 2024, 1:00 PM
Unknown Object (File)
Sep 1 2024, 10:05 PM
Unknown Object (File)
Aug 29 2024, 12:43 PM
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.