JavaScript:SpiderMonkey:C Coding Style: Difference between revisions

* Function return types are on a separate line preceding the function name.

* Function braces go on the line following the function name.

  {

     ...

  }

  void

  {

     ...

* Comment /* FALL THROUGH */ in place of missing break when intentionally falling through from one case-controlled statement sequence into another, or into the default statements.

* Do not use spaces between a function name and its arguments list,                                                or between an array name and the square bracket. Also, do no use spaces after a bracket. Use a space after a comma to separate arguments.

* Use a space between a C keyword and parentheses.

== Indentation and Bracing ==

* Function arguments that overflow the first line of the call expression should be aligned to underhang the first argument (to start in overflow lines in the column after the opening parenthesis).

               cx);

               cx);

* An opening brace is placed on the same line as the preceding statement.

  {

  }

  }

* Do not put compound statements in one line. Indent the controlled statement on the next line, for clarity and break-pointing.

     break;

* If a statement or condition covers multiple lines, use braces for all the controlled statements (even if the else part fits on one line, brace it too).

     CallThisMethod(argument1,

                     argument2);

     CallThisMethod(argument1,

                     argument2);

  MyFunction(int n)

  {

         ...

     }

  {

     if(!n)

     ...

  }

* If an "if" statement controls a "then" clause ending in a return statement, do not use "else" after return.

     DoThis();

     return;

  else

     DoThat();

     DoThis();

     return;

* Avoid similar arbitrary patterns and non-sequiturs:

     DoThis();

     DoThat();

  }

  DoTheOther();

     CleanUp();

     return;