Delegate marking should be at the right location.

Whitespaces and comments skipping should be carried out before
calling the syntax tree delegate location marking functions.

https://code.google.com/p/esprima/issues/detail?id=355
Simplify comment collection.

Instead of two separate functions, now skipComment can also collect all
line and block comments, making scanComment() not necessary anymore.

The most cyclomatic function now falls into scanRegExp().

https://code.google.com/p/esprima/issues/detail?id=396
Include changes for 1.0.3.
Check corner cases of Strict Directive.

Ensure that EscapeSequence and LineContinuation are handled correctly.

https://code.google.com/p/esprima/issues/detail?id=427
Get the sources from upstream projects.

https://code.google.com/p/esprima/issues/detail?id=424
Remove location filter for the comment array.

https://code.google.com/p/esprima/issues/detail?id=417
Implement LocationMarker object type.

This is the master-branch patch analogous to #185, which applies to
the harmony branch.

https://code.google.com/p/esprima/issues/detail?id=429
AMD test: Do not load via script tag explicitly.

The loading of Esprima should be handled by RequireJS.

http://code.google.com/p/esprima/issues/detail?id=291
Remove the need to specialized token handling.

This also get rids of the patch and unpatch pair.

https://code.google.com/p/esprima/issues/detail?id=398
Parsing empty switch contains 'cases' key

SpiderMonkey and the Parser API defined 'cases' to be in the
SwitchStatement production.

https://code.google.com/p/esprima/issues/detail?id=436
Support escaped "]" in regexp literal character classes (ex: "/[\]/]/")

https://code.google.com/p/esprima/issues/detail?id=442

The RegExp expression parser did not handle the escape sequence "\]" within
character classes, or any escape sequence for that matter. Once in a character
class, the parser consumed all characters until reaching "]".

This diff makes the parser always consider escape sequences, whether it is
currently inside of a character class or not. This more closely matches the
grammar, which looks like:

  RegularExpressionChar ::=
    RegularExpressionNonTerminator but not \ or / or [
    RegularExpressionBackslashSequence
    RegularExpressionClass

  ...

  RegularExpressionClassChar ::=
    RegularExpressionNonTerminator but not ] or \
    RegularExpressionBackslashSequence

http://es5.github.io/#x7.8.5

That is, the parser can derive RegularExpressionBackslashSequence both inside
and outside of character classes.

Test plan: Added test case to test.js and loaded it in Chrome 30 and Firefox 25.
These browsers produce different results for `new RegExp('[\\]/]').toString()`
so the test case dynamically computes that value.
Tolerant mode: ignore invalid left-hand side expression.

https://code.google.com/p/esprima/issues/detail?id=81
https://code.google.com/p/esprima/issues/detail?id=130
For Bower, switch to bower.json.

https://code.google.com/p/esprima/issues/detail?id=342
Some keywords for the package manifests.

https://code.google.com/p/esprima/issues/detail?id=4
https://code.google.com/p/esprima/issues/detail?id=342
Minimize the payload for bower.

https://code.google.com/p/esprima/issues/detail?id=342
https://code.google.com/p/esprima/issues/detail?id=362
Support `<!--` comment syntax

https://code.google.com/p/esprima/issues/detail?id=451
Fix wrong handling of relational expression in a for statement.

If operator 'in' is not allowed, it can not be just allowed within
the binary expression.

https://code.google.com/p/esprima/issues/detail?id=449
Accept Ogham Space Mark as whitespace character

https://code.google.com/p/esprima/issues/detail?id=452
Add whitespace tests for line terminator characters

https://code.google.com/p/esprima/issues/detail?id=452
Attach every comment to the possible following syntax node.

The comment is placed in the leadingComments array of the said node.
This is based on the original patch from Yusuke Suzuki.

https://code.google.com/p/esprima/issues/detail?id=197