Prepare for Twitter Bower.

http://code.google.com/p/esprima/issues/detail?id=342
Refactor position tracking.

http://code.google.com/p/esprima/issues/detail?id=344
Change member expression parsing.

Because of the nature of brackets like [] and (), we can't use run-time
patching to capture the position before and after some member expression
parsing routines. The solution is to create a specialized version when
we need to track the syntax node location.

Coverage regression is expected (temporarily) until variation in the
parsing options when running the test suite gets implemented.

http://code.google.com/p/esprima/issues/detail?id=324
http://code.google.com/p/esprima/issues/detail?id=343
Mozilla array comprehensions (de facto), with tests.

http://code.google.com/p/esprima/issues/detail?id=339
"Each" throws specific error.  (updated)

http://code.google.com/p/esprima/issues/detail?id=329

All tests pass. No regressions.

No benchmark impact.
Support ArrayPattern assignment

http://code.google.com/p/esprima/issues/detail?id=346
Rename Quasi to Template

http://code.google.com/p/esprima/issues/detail?id=348
Transpiler demo: allow copying the result.

http://code.google.com/p/esprima/issues/detail?id=282
README: Mention Six and Sweet.js.
Merge commit '1f72370cdda36e5d21a96dcc7a340bd087ee858c' into harmony
An example to detect nested ternary conditionals.

http://code.google.com/p/esprima/issues/detail?id=349
Change member expression parsing.

Because of the nature of brackets like [] and (), we can't use run-time
patching to capture the position before and after some member expression
parsing routines. The solution is to create a specialized version when
we need to track the syntax node location.

Coverage regression is expected (temporarily) until variation in the
parsing options when running the test suite gets implemented.

http://code.google.com/p/esprima/issues/detail?id=324
http://code.google.com/p/esprima/issues/detail?id=343

Conflicts:
	esprima.js
Merge branch 'master' into harmony

Conflicts:
	esprima.js
Vary the parsing test with and without location info.

http://code.google.com/p/esprima/issues/detail?id=343
Speed-up unary expression parsing.

The fast path for parseUnaryExpression() is to go straight to
parsePostfixExpression() function.

V8 version 3.12.19 shows 3.7% speed-up.

http://code.google.com/p/esprima/issues/detail?id=350
Add tests for the grouping operator.

These tests highlight the problem with syntax node location when the
expression contains parentheses.

http://code.google.com/p/esprima/issues/detail?id=345
Workaround for binary expressions containing group operator.

http://code.google.com/p/esprima/issues/detail?id=345
Use the editor properly with IE.

By placing CodeMirror within div instead of p, it won't throw a warning
(exception). This way we don't fall back to plain textarea anymore.

http://code.google.com/p/esprima/issues/detail?id=300
Start ChangeLog.
Speed-up unary expression parsing.

The fast path is when there is no postfix operator.

Safari 6 shows minor 3% improvement on the benchmark suite.

http://code.google.com/p/esprima/issues/detail?id=350