use temp variables in expressions to support multiple yields
Rename the binary to `regenerator`

This is more consistent with the name of the project and avoids ambiguity
with the Regenerate package on npm (http://mths.be/regenerate).
Use `regenerator` instead of `regenerate` consistently
Add reference to ECMAScript wiki with generators information.
Use a relative link for tests reference
Adding a few missing semi-colons
Updated tests script for Node v0.11.7
Merge pull request #29 from mathiasbynens/master

Use `regenerator` instead of `regenerate` more consistently
Merge pull request #23 from bartekn/master

Error information before running tests on Node 0.11.7
Link to draft specification as per @benjamn's suggestion
Bump NPM version to 0.2.0 in preparation for publishing.

The minor version bump is mostly due to #29, which renamed
`bin/regenerate` to `bin/regenerator`.

Also, since we have test coverage as far back as Node.js v0.6, I updated
the "engines" property in `package.json` to reflect that.
Merge pull request #32 from AnSavvides/master

README improvements and cleanup
Make sure the binary works even if it’s not installed globally

Closes #30 and #33.
Merge pull request #33 from mathiasbynens/master

Make sure the binary works even if it’s not installed globally
Support bin/regenerator --include-runtime.

Closes #31.
Encourage global NPM installation in README.md.
Merge pull request #28 from sciolist/master

use temp variables in expressions to support multiple yields
Store "volatile" context properties in temporary variables.

In complicated expressions that contain multiple yield sub-expressions,
like the ones reported in #26 and #28, the values of context properties
like context.sent can get overwritten, so for safety's sake we should
store those values in temporary variables.
Bump NPM version to 0.2.1 in preparation for publishing.
Move runtime-prepending logic into the module API.