我的书签
添加书签
移除书签Our C code has a few style rules. Most of them are verified and upheld by the
lib/checksrc.pl script. Invoked with or even by default by the
build system when built after has been used.
It is normally not a problem for anyone to follow the guidelines as you just
need to copy the style already used in the source code, and there are no
particularly unusual rules in our set of rules.
We also work hard on writing code that is warning-free on all the major
platforms and in general on as many platforms as possible. Code that obviously
will cause warnings will not be accepted as-is.
We use only spaces for indentation, never TABs. We use two spaces for each new
open brace.
Comments
Since we write C89 code, // aren’t allowed. They weren’t introduced in the C
standard until C99. We use only /* and */ comments:
Source code in curl may never be wider than 80 columns. There are two
reasons for maintaining this even in the modern era of very large and high
resolution screens:
Narrower columns allow developers to more easily view multiple pieces of code
next to each other in different windows. I often have two or three source
code windows next to each other on the same screen, as well as multiple
terminal and debugging windows.
Open brace on the same line
In if/while/do/for expressions, we write the open brace on the same line as
the keyword and we then set the closing brace on the same indentation level as
the initial keyword. Like this:
When adding an clause to a conditional expression using braces, we add
it on a new line after the closing brace. Like this:
