PEG.js 0.9.0 released

[David Majda]

Hi,

After a long time, I prepared a new PEG.js release -- PEG.js 0.9.0. The most important changes include:

• Tracing support
• Infinite loop detection
• Improved location information API
• Improved error reporting
• Strict mode code

For more details, see the release page. Note that some changes are not backward-compatible and may break your grammars.

Installation

The easiest way to try the new release is the online version. You can also install it using npm, Bower, WebJar, or use a pre-built browser version. See the installation documentation for details.

Next Releases

The next release of PEG.js will be 0.10.0 -- another milestone on the road to 1.0.0. I plan to publish more detailed roadmap shortly.

Happy parsing!

--

David Majda
Entropy fighter
http://majda.cz/

[ma...@martynjago.co.uk]

On Sunday, August 30, 2015 at 8:45:02 AM UTC+1, David Majda wrote:
> Hi,
>
>
> After a long time, I prepared a new PEG.js release -- PEG.js 0.9.0. The most important changes include:

> Tracing supportInfinite loop detectionImproved location information APIImproved error reportingStrict mode code

> For more details, see the release page. Note that some changes are not backward-compatible and may break your grammars.
>
>
> Installation
>
>
> The easiest way to try the new release is the online version. You can also install it using npm, Bower, WebJar, or use a pre-built browser version. See the installation documentation for details.
>
>
> Next Releases
>
>
> The next release of PEG.js will be 0.10.0 -- another milestone on the road to 1.0.0. I plan to publish more detailed roadmap shortly.
>
>
> Happy parsing!
>
> --
>
> David Majda
> Entropy fighter
> http://majda.cz/

Hi David

Thanks for this release. I'm new to PEG parsers but am enjoying working with pegjs. I really like the new trace functionality.

I'm doing partial PEG parses on sections of streamed C code that I break into `chunks' first (on the fly) - pass in a relevant startRule and parse the chunk (again on the fly), and stream the result out. It is very quick, and I was wondering if this partial parsing was `normal' (rather than parsing the whole thing at once)?

Thanks also for the specs, which helped a lot in how to use some features.

Martyn

[David Majda]

2015-09-02 13:43 GMT+02:00 <ma...@martynjago.co.uk>:

I'm doing partial PEG parses on sections of streamed C code that I break into `chunks' first (on the fly) - pass in a relevant startRule and parse the chunk (again on the fly), and stream the result out. It is very quick, and I was wondering if this partial parsing was `normal' (rather than parsing the whole thing at once)?

It's not an expected and currently supported use case, but people do similar things with PEG.js for performance reasons.

Thanks also for the specs, which helped a lot in how to use some features.

You're welcome :-)

[to...@subfuzion.com]

Awesome! It's great to see the update published to npm. I had a gist for node devs recommending adding the GitHub url as a dependency instead of the npm package, but I've updated it now. Thank you for PEG.js!

https://gist.github.com/tonypujals/808f91bfdfb88c7d5ed7

On Sunday, August 30, 2015 at 12:45:02 AM UTC-7, David Majda wrote:
> Hi,
>
>
> After a long time, I prepared a new PEG.js release -- PEG.js 0.9.0. The most important changes include:

> Tracing supportInfinite loop detectionImproved location information APIImproved error reportingStrict mode code