[pro] Is cl-yacc going to cut it?

[Matthew D. Swank]

Meta does seem like a parser for people allergic to parsing.  Of course
it has a great lisp pedigree as well. I am biased by early exposure to
Ken Thompson's work on regular expressions and LALR parsers.

Matt
 
On 02/04/2011 09:31 AM, Thomas M. Hermann wrote:
> I am absolutely biased towards meta-sexp:
>
> "A META parser generator using LL(1) grammars with s-expressions."
>
> https://github.com/vy/meta-sexp
>
> It seems dirt simple to use, at least to me and the performance has
> been acceptable.
>
> Regards,
>
> ~ Tom
> ----------------------------------------------------------------
> Thomas M. Hermann
> Odonata Research LLC
> http://www.odonata-research.com/
> http://www.linkedin.com/in/thomasmhermann
>
>
> On Fri, Feb 4, 2011 at 9:20 AM, Nikodemus Siivola
> <nikodemus at random-state.net <mailto:nikodemus at random-state.net>> wrote:
>
>     On 4 February 2011 16:39, Paul Tarvydas <paul.tarvydas at rogers.com
>     <mailto:paul.tarvydas at rogers.com>> wrote:
>
>     > The relatively new PEG packrat parser technologies make it possible
>     > to use just one universal description for, both, scanning and
>     >  parsing.  I see that cl-peg exists, but I haven't tried it out.
>
>     Esrap is another packrat parser for CL:
>
>      https://github.com/nikodemus/esrap
>
>     I had to parse some semi-structured text and wrote Esrap for that. Its
>     primary limitations are lacking support for parsing from streams (it
>     wants a string) and very little documentation.
>
>     Cheers,
>
>      -- Nikodemus
>
>     _______________________________________________
>     pro mailing list
>     pro at common-lisp.net <mailto:pro at common-lisp.net>
>     http://common-lisp.net/cgi-bin/mailman/listinfo/pro
>
>
>
> _______________________________________________
> pro mailing list
> pro at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/pro

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/pro/attachments/20110204/fac7e213/attachment.html>