Skip to content

Commit

Permalink
coding style: allow lines up to 160 chars in length
Browse files Browse the repository at this point in the history
Avi writes,

> We promote long, explanatory names instead of acronyms. If we fold too
> much we end up taking a lot of vertical space and functions no longer
> fit on a screen.

Suggested-by: Avi Kivity <[email protected]>
Signed-off-by: Laszlo Ersek <[email protected]>
  • Loading branch information
lersek authored and avikivity committed Jul 16, 2024
1 parent a3ccb7a commit bd27a45
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion coding-style.md
Original file line number Diff line number Diff line change
Expand Up @@ -127,7 +127,7 @@ Whitespace around operators should match their precedence: high precedence = no

## Long lines

If a line becomes excessively long (>120 characters?), or is just complicated, break it into two or more lines. The second (and succeeding lines) are _continuation lines_, and have a double indent:
If a line becomes excessively long (>160 characters?), or is just complicated, break it into two or more lines. The second (and succeeding lines) are _continuation lines_, and have a double indent:

```c++
if ((some_condition && some_other_condition)
Expand Down

0 comments on commit bd27a45

Please sign in to comment.