Browse code

More about coding style

git-svn-id: file:///var/lib/svn/clamav-devel/trunk/clamav-devel@2032 77e5149b-7576-45b1-b177-96237e5ba77b

Nigel Horne authored on 2006/06/20 17:20:18
Showing 1 changed files
... ...
@@ -319,7 +319,13 @@ Running in the foreground, valgrind, LogSyslog, LogVerbose, LogFile etc.
319 319
 5.1. Patches
320 320
 
321 321
 Patches are welcome, but they must be against the latest CVS version and adhere
322
-to the coding style of clamav-milter. Most of this style is based on K&R.
322
+to the coding style of clamav-milter. Coding style is religious, everyone
323
+believes theirs is great and all others are fine.
324
+
325
+This is my coding style, live with it. You don't want me in a bad mood because
326
+I can't read your code when I'm deciding if your code should be incorporated.
327
+
328
+Most of this style is based on K&R.
323 329
 
324 330
 Use the tab key, not space key, to indent.
325 331
 
... ...
@@ -343,6 +349,9 @@ Sun's cc).
343 343
 
344 344
 Function names appear at the start of lines (I use ctags).
345 345
 
346
+Document your changes. If you add, remove, or change functionality you will
347
+need to update the manual page and possibly the usage message as well.
348
+
346 349
 6. TODO
347 350
 
348 351
 There are several ideas marked as TODO in the source code. If anyone has