Difference between revisions of "Programming Guideline Checklist"

From Dreamwidth Notes
Jump to: navigation, search
(Created page with 'This is a quick checklist of the Dev Programming Guidelines page; go there for details. == Code Formatting == * Check for whitespace: ** Four spaces for indentation. No ta...')
 
m
Line 16: Line 16:
 
== DW Code Specific Conventions ==
 
== DW Code Specific Conventions ==
  
* Use <tt>LJ::HOME</tt> over $ENV{LJHOME}
+
* Use <tt>$LJ::HOME</tt> over $ENV{LJHOME}
 
* Use <tt>LJ::is_enabled()</tt> over $LJ::DISABLED
 
* Use <tt>LJ::is_enabled()</tt> over $LJ::DISABLED
 
* Use <tt>$u->get_cap</tt> over <tt>LJ::get_cap($u, ...)</tt> (or add an accessor in <tt>LJ::User</tt>)
 
* Use <tt>$u->get_cap</tt> over <tt>LJ::get_cap($u, ...)</tt> (or add an accessor in <tt>LJ::User</tt>)

Revision as of 07:17, 25 March 2009

This is a quick checklist of the Dev Programming Guidelines page; go there for details.

Code Formatting

  • Check for whitespace:
    • Four spaces for indentation. No tabs.
    • No trailing whitespace.
    • Spaces around parenthesis and operators. A space between if and the starting parens, spaces between method arg parens, etc. Do not use spaces around hash indexes, however.
    • Suggested line break length at 120 characters.
  • Do not use extraneous parentheses, including on methods that don't need it or on postfix conditionals.
  • Use postfix conditionals -- ie, do_something() if $something;
  • Use human logic -- unless instead of if not.
  • Don't quote hash literals -- $HASH{DATA}, not $HASH{'DATA'}
  • Commenting: have you commented appropriately?

DW Code Specific Conventions

  • Use $LJ::HOME over $ENV{LJHOME}
  • Use LJ::is_enabled() over $LJ::DISABLED
  • Use $u->get_cap over LJ::get_cap($u, ...) (or add an accessor in LJ::User)
  • English stripping is required for pages!
  • New files need appropriate header/credit