chiark
/
gitweb
/
~ianmdlvl
/
elogind.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
test-compress: also test with incompressible inputs
[elogind.git]
/
CODING_STYLE
diff --git
a/CODING_STYLE
b/CODING_STYLE
index ca3b5183f901037a1e6b201e13f231f86fa8b9db..05b5ecf89f32835e0ed1b6ee3463c035b5a8e4aa 100644
(file)
--- a/
CODING_STYLE
+++ b/
CODING_STYLE
@@
-1,6
+1,9
@@
-
- 8ch indent, no tabs
- 8ch indent, no tabs
+- Don't break code lines too eagerly. We do *not* force line breaks at
+ 80ch, all of today's screens should be much larger than that. But
+ then again, don't overdo it, ~140ch should be enough really.
+
- Variables and functions *must* be static, unless they have a
prototype, and are supposed to be exported.
- Variables and functions *must* be static, unless they have a
prototype, and are supposed to be exported.
@@
-152,7
+155,7
@@
function or a "non-logging" function. "Logging" functions do logging
on their own, "non-logging" function never log on their own and
expect their callers to log. All functions in "library" code,
function or a "non-logging" function. "Logging" functions do logging
on their own, "non-logging" function never log on their own and
expect their callers to log. All functions in "library" code,
- i.e. in src/shared/ and suchlike must be "non-logging". Everytime a
+ i.e. in src/shared/ and suchlike must be "non-logging". Every
time a
"logging" function calls a "non-logging" function, it should log
about the resulting errors. If a "logging" function calls another
"logging" function, then it should not generate log messages, so
"logging" function calls a "non-logging" function, it should log
about the resulting errors. If a "logging" function calls another
"logging" function, then it should not generate log messages, so