Confirmed users
586
edits
Fennec/NativeUI/CodingStyle: Difference between revisions
Jump to navigation
Jump to search
→Java: clarify some things
No edit summary |
(→Java: clarify some things) |
||
| Line 10: | Line 10: | ||
== Java == | == Java == | ||
* We use the [http://www.oracle.com/technetwork/java/codeconvtoc-136057.html Java Coding Style]. | * We use the [http://www.oracle.com/technetwork/java/codeconvtoc-136057.html Java Coding Style]. Quick summary: | ||
** FirstLetterUpperCase for class names | |||
** camelCase for method and variable names | |||
** One declaration per line | |||
int x, y; // this is BAD! | |||
int a; // split it over | |||
int b; // two lines | |||
** Braces should be placed like so (generally opening braces on same line, closing braces on a new line): | |||
public void func(int arg) { | |||
if (arg != 0) { | |||
while (arg > 0) { | |||
arg--; | |||
} | |||
} else { | |||
arg++; | |||
} | |||
} | |||
* Places we differ from the Java coding style: | |||
** Start class variable names with m (e.g. mSomeClassVariable) | |||
** Don't use wilcard imports. | |||
** 4-space indents | |||
** spaces, not tabs | |||
** Don't restrict yourself to 80-character lines. Java code tends to be long horizontally, so use appropriate judgement when wrapping. Avoid deep indents on wrapping. Note that aligning the wrapped part of a line with some previous part of the line (rather than just using a fixed indent) may require shifting the code every time the line changes, resulting in spurious whitespace changes. | |||
* The [http://source.android.com/source/code-style.html Android Coding Style] has some useful guidelines too. | * The [http://source.android.com/source/code-style.html Android Coding Style] has some useful guidelines too. | ||