aboutsummaryrefslogtreecommitdiffstats
path: root/doc/CODING-GUIDELINES
diff options
context:
space:
mode:
authormarkster <markster@f38db490-d61c-443f-a65b-d21fe96a405b>2004-05-15 15:34:31 +0000
committermarkster <markster@f38db490-d61c-443f-a65b-d21fe96a405b>2004-05-15 15:34:31 +0000
commit83ced88193d5b1a297c0ecbad0a365a0d3fad806 (patch)
tree4668e67ff52f9fa3f3f82ffa004d51511256d331 /doc/CODING-GUIDELINES
parentf6bf7467fe26fd7fde129fe3995ec807894b24bc (diff)
Update coding guidelines, fix "say.c" compile on older compilers, update coding guidelines (includes bug #1631)
git-svn-id: http://svn.digium.com/svn/asterisk/trunk@2967 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'doc/CODING-GUIDELINES')
-rwxr-xr-xdoc/CODING-GUIDELINES5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/CODING-GUIDELINES b/doc/CODING-GUIDELINES
index 7d621b48d..04b5b38d9 100755
--- a/doc/CODING-GUIDELINES
+++ b/doc/CODING-GUIDELINES
@@ -6,6 +6,11 @@ see http://bugs.digium.com
Patches should be in the form of a unified (-u) diff.
+All code, filenames, function names and comments must be in ENGLISH.
+
+Do not declare variables mid-function (e.g. like GNU lets you) since it is
+harder to read and not portable to GCC 2.95 and others.
+
Don't annotate your changes with comments like "/* JMG 4/20/04 */";
Comments should explain what the code does, not when something was changed
or who changed it.