mirror of
https://github.com/curl/curl.git
synced 2026-04-14 22:21:41 +03:00
stop using the word 'just'
Everywhere. In documentation and code comments. It is almost never a good word and almost always a filler that should be avoided. Closes #20793
This commit is contained in:
parent
4b583b7585
commit
b4dba346cd
213 changed files with 727 additions and 772 deletions
|
|
@ -19,9 +19,9 @@ Our C code has a few style rules. Most of them are verified and upheld by the
|
|||
by the build system when built after `./configure --enable-debug` 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.
|
||||
It is normally not a problem for anyone to follow the guidelines, simply 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 are warning-free on all the major
|
||||
platforms and in general on as many platforms as possible. Code that causes
|
||||
|
|
@ -39,7 +39,7 @@ understand it when debugging.
|
|||
|
||||
Try using a non-confusing naming scheme for your new functions and variable
|
||||
names. It does not necessarily have to mean that you should use the same as in
|
||||
other places of the code, just that the names should be logical,
|
||||
other places of the code, only that the names should be logical,
|
||||
understandable and be named according to what they are used for. File-local
|
||||
functions should be made static. We like lower case names.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue