Instaparse <https://github.com/Engelberg/instaparse/> is an easy-to-use,
feature-rich parser library.  The big idea behind instaparse is to make it
simple to convert grammars to parsers without needing to know the
idiosyncrasies of LL1, LALR, and other esoteric grammar restrictions
imposed by most parser generators.

Here are the highlights of the new 1.2.0 release:

1. Several significant performance improvements.

2. Two new functions, `span` and `visualize` which allow you to better
understand the structure of your parse tree.
https://github.com/Engelberg/instaparse/#understanding-the-tree

3. A new optional keyword argument to `parse` and `parses` that allows you
to reveal hidden information, primarily for debugging purposes.
https://github.com/Engelberg/instaparse/#revealing-hidden-information


I've received a few questions from instaparse users who wanted to know if I
had any performance tips.  Since version 1.2.0 is primarily a
performance-oriented release, it seemed fitting to include, as part of the
release, a list of performance tips as well as an expanded essay about
instaparse's performance and what I'm striving for.

https://github.com/Engelberg/instaparse/blob/master/docs/Performance.md


Thanks to everyone who provided feature requests on the github site, and
especially to those who tracked along with the 1.2.0-SNAPSHOT releases and
provided feedback for this new release.

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to