STYLE 781 B raw
1
* Separate function definitions with a blank line. If a function has a
2
comment, put the blank line before the comment.
3
* Groups of function prototypes do not need blank lines between them or
4
before their comments.
5
* Put standard and system headers first. Put third-party headers next,
6
  followed by project headers. Separate these groups with a blank line.
7
* Include project headers with quotes. Use paths relative to the source
8
  directory or the project root. Do not use parent directory components.
9
* Use short, clear variable and field names. Avoid names that make
10
declarations difficult to align.
11
* Keep struct fields and their comments aligned. Keep trailing comments
12
short. Put longer comments above the fields they describe. Make sure struct
13
fields align after formatting.