CODING_STYLE.rst: Be less strict about 80 character limit
Relax the wording about line lengths a little bit; this goes with the checkpatch changes to warn at 100 characters rather than 80. (Compare the Linux kernel commit bdc48fa11e46f8; our coding style is not theirs, but the rationale is good and applies to us too.) Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Reviewed-by: Markus Armbruster <armbru@redhat.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Message-Id: <20201106112940.31300-1-peter.maydell@linaro.org> Signed-off-by: Laurent Vivier <laurent@vivier.eu>
This commit is contained in:
parent
87b804ec4c
commit
a998de0dcd
@ -85,8 +85,13 @@ Line width
|
||||
Lines should be 80 characters; try not to make them longer.
|
||||
|
||||
Sometimes it is hard to do, especially when dealing with QEMU subsystems
|
||||
that use long function or symbol names. Even in that case, do not make
|
||||
lines much longer than 80 characters.
|
||||
that use long function or symbol names. If wrapping the line at 80 columns
|
||||
is obviously less readable and more awkward, prefer not to wrap it; better
|
||||
to have an 85 character line than one which is awkwardly wrapped.
|
||||
|
||||
Even in that case, try not to make lines much longer than 80 characters.
|
||||
(The checkpatch script will warn at 100 characters, but this is intended
|
||||
as a guard against obviously-overlength lines, not a target.)
|
||||
|
||||
Rationale:
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user