Good Coding Style Guidelines
| Aspect of JavaScript: Recommendation |
| Variable identifiers |
| Use camel-back capitalization and descriptive names that give an indication of what value the variable might be expected to hold. Appropriate variable names are most often made up of one or more nouns. |
| Function identifiers |
| Use the camel-back capitalization and descriptive names that indicate what operation they carry out. Appropriate function names are most often made up of one or more verbs. |
| Variable declarations |
| Avoid implicitly declared variables as they clutter the global namespace and lead to confusion. Always use var to declare your variables in the most specific scope possible. Avoid global variables whenever possible. |
| Functions |
| Pass values that need to be modified by reference by wrapping them in a composite type. Or, alternatively, return the new value that the variable should take on. Avoid changing global variables from inside functions. Declare functions in the document <head> or in a linked .js library. |
| Constructors |
| Indicate that object constructors are such by capitalizing the first letter of their identifier. |
| Comments |
| Use comments liberally. Complex conditionals should always be commented and so should functions. |
| Indentation |
| Indent each block two to five spaces further than the enclosing block. Doing so gives visual cues as to nesting depth and the relationship between constructs like if/else. |
| Modularization |
| Whenever possible, break your scripts up into externally linked libraries. Doing so facilitates code reuse and eases maintenance tasks. |
| Semicolons |
| Use them. Do not rely on implicit semicolon insertion. |
No comments :
Post a Comment