On Sun, Oct 5, 2014 at 7:24 AM, Isiah Meadows <impinball at gmail.com> wrote:

> If I can find a native parser (that only parses), I would run benchmarks.
> Shouldn't take that long to time a few rounds of parsing a large library
> like jQuery or React. I would be more than willing to accept pointers on
> where to find one.
>
The SpiderMonkey shell lets you do both syntax parsing - the fast initial
parse we do to detect static errors, and full parsing; both using the same
parser Firefox uses. You can download the latest version here:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/

Or, for non-dev build versions, check one directory up.

The shell has a `parse` function for full parsing and a `parseSyntax` for,
well, syntax parsing. More information available using `help()`.


hth,
till
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20141006/3f91dd47/attachment.html>

On Sun, Oct 5, 2014 at 7:24 AM, Isiah Meadows <impinball at gmail.com> wrote:

> If I can find a native parser (that only parses), I would run benchmarks.
> Shouldn't take that long to time a few rounds of parsing a large library
> like jQuery or React. I would be more than willing to accept pointers on
> where to find one.
>

The SpiderMonkey shell lets you do both syntax parsing - the fast initial
parse we do to detect static errors, and full parsing; both using the same
parser Firefox uses. You can download the latest version here:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/

Or, for non-dev build versions, check one directory up.

The shell has a `parse` function for full parsing and a `parseSyntax` for,
well, syntax parsing. More information available using `help()`.