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
Move the tests for HTML comment.

These are not only for tolerant mode, place them in the Comment category.

https://code.google.com/p/esprima/issues/detail?id=451
Support --> HTML comment.

From http://javascript.spec.whatwg.org/#comment-syntax:

  --> at the start of a line, optionally preceded by whitespace or
  MultiLineComments, must be treated as a SingleLineComment
  — equivalent to //.

https://code.google.com/p/esprima/issues/detail?id=451
Regular expression can not have LineTerminator.

https://code.google.com/p/esprima/issues/detail?id=454
Remove unnecessary file.

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

The comment is placed in the trailingComments 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
Fix the attachment of comments.

Both the proximity and the size of each syntax node need to be taken
into account when deciding which comment must be attached.

https://code.google.com/p/esprima/issues/detail?id=197
Add Node script to generate the identifier regexes.

The script was taken from https://gist.github.com/mathiasbynens/6334847
and then modified to match Esprima’s needs.

It replaces the Python script that was previously used for the same
purpose. The new script is simpler, more compact, and doesn’t require
any manual post-processing of the data.

https://code.google.com/p/esprima/issues/detail?id=110
Update some files in the benchmark corpus.

Updated libraries:
- Underscore.js 1.5.2
- jQuery Mobile 1.3.2
- AngularJS 1.0.8
- YUI 3.12.0

https://code.google.com/p/esprima/issues/detail?id=354
Update the fixture for the parsing smoke tests.

https://code.google.com/p/esprima/issues/detail?id=425
Fix for tokenizing and regex

When running tokenize on code with regular expression literals
the order of tokens would sometimes be off and extra tokens inserted.
This was due to peek being called before scanRegExp finished adding
the literal to extra.tokens.

http://code.google.com/p/esprima/issues/detail?id=446
Add manifest file for component.io.

https://code.google.com/p/esprima/issues/detail?id=459
Ensure consistent library version across different files.

https://code.google.com/p/esprima/issues/detail?id=470
Remove spurious trailing comma.

https://code.google.com/p/esprima/issues/detail?id=417
Use ESLint to lint the code.

https://code.google.com/p/esprima/issues/detail?id=473
esparse should handle regular expression literals.

As suggested by Arian Stolwijk.

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