summaryrefslogtreecommitdiffstats
path: root/contrib/ipfilter/STYLE.TXT
diff options
context:
space:
mode:
authordarrenr <darrenr@FreeBSD.org>2005-04-25 17:31:50 +0000
committerdarrenr <darrenr@FreeBSD.org>2005-04-25 17:31:50 +0000
commitd438802dcb3e270d6fcc65f075c808c64853a7c2 (patch)
treee2e1c7115044e6dfc86ff65598566fa32e5f7421 /contrib/ipfilter/STYLE.TXT
parent590450fec65a8e72a8965117398bc8f14938b4a8 (diff)
downloadFreeBSD-src-d438802dcb3e270d6fcc65f075c808c64853a7c2.zip
FreeBSD-src-d438802dcb3e270d6fcc65f075c808c64853a7c2.tar.gz
import ipfilter 4.1.8 into the vendor branch
Diffstat (limited to 'contrib/ipfilter/STYLE.TXT')
-rw-r--r--contrib/ipfilter/STYLE.TXT57
1 files changed, 57 insertions, 0 deletions
diff --git a/contrib/ipfilter/STYLE.TXT b/contrib/ipfilter/STYLE.TXT
new file mode 100644
index 0000000..384bcec
--- /dev/null
+++ b/contrib/ipfilter/STYLE.TXT
@@ -0,0 +1,57 @@
+
+Over time, I am moving all of the IPFilter code to what I consider a better
+coding style than it had before. If you submit patches, I expect them to
+conform as appropriate.
+
+Function Comments
+=================
+Preceeding each and every function, a comment block like this should
+be present:
+
+/* ------------------------------------------------------------------------ */
+/* Function: function-name */
+/* Returns: return-type */
+/* Parameters: param1(I) - param1 is an input parameter */
+/* p2(O) - p2 is an output parameter passed as an arg */
+/* par3(IO) - par3 is a parameter which is both input and */
+/* output. Pointers to things which are used and */
+/* then get a result stored in them qualify here. */
+/* */
+/* Description about what the function does. This comment should explain */
+/* any gotchas or algorithms that are used which aren't obvious to the */
+/* casual reader. It should not be an excuse to not use comments inside */
+/* the function. */
+/* ------------------------------------------------------------------------ */
+
+
+Tab spacing
+===========
+Tabs are to be at 8 characters.
+
+
+Conditions
+==========
+All expressions which evaluate to a boolean for a test condition, such as
+in an if()/while() statement must involve a boolean operation. Since C
+has no native boolean type, this means that one of <,>,<=,>=,==,!= must
+be present. Implied boolean evaluations are out.
+
+In code, the following is banned:
+
+if (x)
+if (!x)
+while ((a = b))
+
+and should be replaced by:
+
+if (x != 0)
+if (x == 0)
+while ((a = b) != 0)
+
+If pointers are involved, always compare with NULL, ie.:
+
+if (x != NULL)
+if (x == NULL)
+while ((a = b) != NULL)
+
+
OpenPOWER on IntegriCloud