The TWG coding standards committee is announcing two coding standards changes for final discussion. These appear to have reached a point close enough to consensus for final completion. The new process for proposing and ratifying changes is documented on the coding standards project page.

New issues for discussion:

• Prefer != to <> for NOT EQUALS
• [policy] Define coding standards for anonymous functions (closures)

Updates on existing issues:

• Stop disallowing camelCase for local variables / parameters - is approved and in the core queue for official core approval.
• [Policy, no patch] PHP 5.4 short array syntax coding standards
• Should we require a blank line after <?php? is approved by core and sniff implemented in coder - ratification of this rule is pending.
• Allow camelCase also for local variables / parameters (the committee is drafting a comment)
• [policy, no patch] Standardize indenting on chained method calls has been moved to the core queue for core approval.
• Add type hinting to function declaration coding standards has been moved to the core queue for core approval.
• [Policy, no patch] Delete permission to pad spacing in a block of related assignments has been marked "needs work" and discussion continues for now. Committee to reevaluate.
• [Policy, no patch] PHP 5.4 short array syntax coding standards Currently marked "needs work" but discussion appears to have stalled. Committee to review at next meeting.

These proposals will be re-evaluated during the next coding standards meeting currently scheduled for July 12. At that point the discussion will likely be extended, or if clear consensus has been reached one or more policies may be dismissed or ratified and moved to the next step in the process.