Mailing-List: contact commits-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Tue, 30 Nov 2010 13:45:14 -0000
Message-ID: <20101130134514.60656.83814@eosnew.apache.org>
Subject: 
 =?utf-8?q?=5BCouchdb_Wiki=5D_Trivial_Update_of_=22Coding=5FStandards=22_b?=
 =?utf-8?q?y_RobertNewson?=

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for c=
hange notification.

The "Coding_Standards" page has been changed by RobertNewson.
The comment on this change is: Use a numbered list instead of bullet points.
http://wiki.apache.org/couchdb/Coding_Standards?action=3Ddiff&rev1=3D3&rev2=
=3D4

--------------------------------------------------

  =

  First, some general rules:
  =

-  * Always use spaces for indentation, not tabs, except in Makefiles.
+  1. Always use spaces for indentation, not tabs, except in Makefiles.
-  * Use four spaces for indentation in Erlang and C code, two spaces in HT=
ML, CSS, and Javascript.
+  1. Use four spaces for indentation in Erlang and C code, two spaces in H=
TML, CSS, and Javascript.
-  * Try to keep lines shorter than 80 characters.
+  1. Try to keep lines shorter than 80 characters.
-  * When you edit a file, try to stick with the conventions used in the su=
rrounding code.
+  1. When you edit a file, try to stick with the conventions used in the s=
urrounding code.
-  * Avoid trailing spaces and newlines in your files. Good editors usually=
 have a configuration option that prevents this from happening.
+  1. Avoid trailing spaces and newlines in your files. Good editors usuall=
y have a configuration option that prevents this from happening.
-  * Avoid mixing purely cosmetic changes (such as removing trailing white-=
space) with functional changes, as that makes review of the actual change (=
whether it=E2=80=99s a check-in or a patch) much more difficult.
+  1. Avoid mixing purely cosmetic changes (such as removing trailing white=
-space) with functional changes, as that makes review of the actual change =
(whether it=E2=80=99s a check-in or a patch) much more difficult.
  =

  For more detailed coding conventions for Erlang code, please see the [[ht=
tp://www.erlang.se/doc/programming_rules.shtml|Erlang Programming Rules and=
 Conventions]].
 =20