* [parisc-linux] Code Readability
@ 1999-10-23 0:33 Philipp Rumpf
0 siblings, 0 replies; only message in thread
From: Philipp Rumpf @ 1999-10-23 0:33 UTC (permalink / raw)
To: parisc-linux
As there already seems to be a discussion going on about this, here's a list
of things I would change in order to save developers time; this is obviously
biased towards developers who spent some time doing this, not towards those
new to the code.
- get rid of the cvs $Log$s. Not only do they tend to get longer than the
code in question, they also seem to be downright boring to me. The only
information you need in the common case is "who was the last one to modify
this file" which $Id$ does just fine.
- use #if 0 (or #ifdef SOMETHING) instead of "/*" to comment out sections of
code more than one line long.
- try to avoid using C++-style "//" line comments, or any comment style except
the usual one, which is
line; /* line comment */
/*
* long comment
* ...
*/
- if you use #ifdef SOMETHING_DEBUG to conditionally compile sanity checks,
put an #undef SOMETHING_DEBUG or #define SOMETHING_DEBUG at the top of the
file. If it is a header file, you don't want to run into problems because
#define SOMETHING_DEBUG is in some .c files and not in others.
- stay with standard linux names. We're pretty good at that.
- look at Documentation/CodingStyle once in a while, especially Chapter 4
Philipp Rumpf
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~1999-10-23 0:32 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
1999-10-23 0:33 [parisc-linux] Code Readability Philipp Rumpf
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.