couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Couchdb Wiki] Trivial Update of "Coding_Standards" by RobertNewson
Date Tue, 30 Nov 2010 13:45:14 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change 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=diff&rev1=3&rev2=4

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

  
  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 HTML, CSS, and Javascript.
+  1. Use four spaces for indentation in Erlang and C code, two spaces in HTML, 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 surrounding code.
+  1. When you edit a file, try to stick with the conventions used in the surrounding 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 usually 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’s 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’s a check-in or a patch)
much more difficult.
  
  For more detailed coding conventions for Erlang code, please see the [[http://www.erlang.se/doc/programming_rules.shtml|Erlang
Programming Rules and Conventions]].
  

Mime
View raw message