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
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)
Created brace-style rule.

The brace-style rule enforces the one true brace style, meaning that the opening curly brace of a block must be placed on the same line as its corresponding statement or declaration.

The rule is defaulted to off.
Merge branch 'master' of https://github.com/nzakas/eslint into ok

Conflicts:
	package.json
Adds test and fix for issue #82
Merge pull request #71 from Constellation/estraverse-controller

Don't report no-empty warnings when a parent is FunctionExpression / FunctionDeclaration
Merge pull request #73 from iancmyers/rule-one-true-brace

Rule: One True Brace Style
Enabled require("eslint") and exposed out CLI.

I've added the "main" key to the package.json, pointing it to lib/api.js. The api.js file exports /lib/eslint.js and /lib/cli.js. This enables those who have run `npm install eslint` to then require eslint in their project like so:

var eslint = require("eslint");

Prior to this change calling `require("eslint")` would throw an error.

In addition, developers can now use the CLI from their projects, without having to `require` it from the `node_modules` directory (which is generally not good). Developers can now use the CLI programatically, like so:

var eslint = require("eslint");
eslint.cli.execute(["-h"]);
Merge pull request #80 from iancmyers/fix-require

Enabled require("eslint") and exposed out CLI.
Rule: The Function constructor is eval
Test to make sure empty case with one line break is safe
Fixing -c config option.

This fixes an issue with the -c (--config) option where the specified config file's path would be resolved from the cli.js directory path instead of process execution directory path, causing an error.

For example, if the user is in `~/project-dir/` and runs `eslint -c special-config.json lint-me.js`, the CLI would try to require `special-config.json` from `~/project-dir/node_modules/eslint/lib/special-config.json` instead of the intended `~/project-dir/special-config.json`.

Changing `__dirname` to `process.pwd()` resolves the issue.
Fixes issue with fs.existsSync on NodeJS 0.6

Fixes an issue where`lib/cli.js` was using `fs.existsSync`, which prior to NodeJS 0.8 was `path.existsSync`. So, on NodeJS 0.6, the CLI would throw an error.
Fixes #90 -- updates docstrings
Add rule for implied eval via setTimeout/Interval