From ce7b81dd5af4aacc16fb2ff974faee4325aba20f Mon Sep 17 00:00:00 2001 From: Bjørn Lindeijer Date: Tue, 14 Dec 2004 22:18:31 +0000 Subject: Mainly been rewriting the guide to compiling TMW on Windows --- docs/HACKING.txt | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) (limited to 'docs/HACKING.txt') diff --git a/docs/HACKING.txt b/docs/HACKING.txt index 6f34b383..b36f5e2a 100644 --- a/docs/HACKING.txt +++ b/docs/HACKING.txt @@ -7,7 +7,8 @@ standard specifying how code is written down. Not doing so can cause quite some annoyance for certain coders and easily creates more version conflicts than necessary. -* Code is indented using 4 spaces, no tabs. +* Indentation: + Code is indented using 4 spaces, no tabs. * Control constructs like this: @@ -24,6 +25,7 @@ necessary. /* * Documentation about behaviour + * ... */ void function(param1, param2) { } @@ -32,6 +34,13 @@ necessary. }; Ending parenthesis may be on next line for clarity. + + Bad: + + if (condition) + statement; + + if (condition) statement; * Use of whitespace example: -- cgit v1.2.3-60-g2f50