Rule to add no-fall-through
Globals are not good, declare len
Merge branch 'master' of https://github.com/nzakas/eslint into rule-fall-through

Conflicts:
	conf/eslint.json
Allow return, falls-through comment, and throw for falls-through
Add rule for missing radix argument to parseInt
Follow the rule naming conventions
Ensure estraverse version 1.2.0 or later
Add api.getAncestors
Don't report no-empty warnings when a parent is FunctionExpression / FunctionDeclaration

(fixes #70)
Adds test and fix for no-octal on 0 literal
Fix the positive case for no-unreachable where there is no return
statement at all, or if the return is at the end. Those cases should not
return any errors. The error condition was not be checked before
throwing the rule error.
Merge pull request #74 from jrfeenst/master

Fix the positive case for no-unreachable
Add EditorConfig file for consistent editor/IDE behavior
Merge pull request #72 from mamacdon/no-octal-0

Adds test and fix for no-octal on 0 literal
Adds smarter-eqeqeq rule
Rule: Do not use 'new' for side effects
Merge pull request #67 from jedhunsaker/editorconfig

Add EditorConfig file for consistent editor/IDE behavior
Merge pull request #75 from goatslacker/smarter-eqeqeq-rule

Adds smarter-eqeqeq rule
Merge pull request #79 from ilyavolodin/no-new

Rule: Do not use 'new' for side effects
Formatters can now process multiple files at once