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
F18796474: D11255.diff
Fri, Oct 17, 3:35 AM
F18764798: D11255.diff
Tue, Oct 7, 7:56 AM
F18637024: D11255.id27015.diff
Sep 17 2025, 5:49 AM
F18624900: D11255.id27014.diff
Sep 15 2025, 9:22 PM
F18597151: D11255.diff
Sep 13 2025, 2:14 AM
F18089105: D11255.diff
Aug 6 2025, 10:25 AM
F18084852: D11255.id.diff
Aug 5 2025, 5:57 PM
F18082396: D11255.id27014.diff
Aug 5 2025, 5:48 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.