003 File Manager
Current Path:
/usr/src/contrib/ipfilter
usr
/
src
/
contrib
/
ipfilter
/
📁
..
📄
BNF
(3.52 KB)
📄
BugReport
(409 B)
📄
HISTORY
(55.43 KB)
📄
LICENCE
(612 B)
📄
Makefile
(14.48 KB)
📄
NAT.FreeBSD
(2.84 KB)
📄
README
(4.53 KB)
📄
STYLE.TXT
(1.96 KB)
📄
WhatsNew50.txt
(2.26 KB)
📄
Y2K
(48 B)
📄
arc4random.c
(5.03 KB)
📄
bpf-ipf.h
(13.72 KB)
📄
bpf_filter.c
(12.32 KB)
📄
genmask.c
(1.14 KB)
📄
ip_dstlist.c
(43.79 KB)
📄
ip_dstlist.h
(1.43 KB)
📄
ip_fil.c
(14.13 KB)
📄
ip_fil_compat.c
(122.12 KB)
📄
ip_msnrpc_pxy.c
(6.25 KB)
📄
ipf.h
(11.97 KB)
📄
ipf_rb.h
(10.37 KB)
📁
iplang
📄
ipmon.h
(3.27 KB)
📁
ipsend
📄
ipt.h
(536 B)
📄
kmem.h
(526 B)
📁
l4check
📁
lib
📁
man
📄
md5.c
(11.36 KB)
📄
md5.h
(3.11 KB)
📄
mkfilters
(2.62 KB)
📄
mlfk_rule.c
(1.23 KB)
📄
opt_inet6.h
(14 B)
📄
opts.h
(1.45 KB)
📄
pcap-ipf.h
(642 B)
📄
radix_ipf.c
(41.92 KB)
📄
radix_ipf.h
(2.64 KB)
📁
rules
📁
samples
📄
snoop.h
(664 B)
📁
sys
📁
tools
Editing: STYLE.TXT
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)
Upload File
Create Folder