I just pushed a utility to the CPAN that really helped me speed up finding 
the error in the grammar I was playing with day before yesterday: 
MarpaX::Tester (https://metacpan.org/pod/MarpaX::Tester), which also 
provides a command-line marpa-test utility.  There are still some rough 
edges, obviously, but essentially the idea is to allow you to write just 
the grammar, get it compiling with Marpa, then throw test texts at it to 
see what works and what doesn't. It spits out Data::Dumper ASTs (or 
whatever your recognizer value is, actually, but since there's no way to 
include external code yet, that's quasi-moot - I guess it would do OK on 
blessed structures).

It turned finding this error from "Oh God what can I look for" to "let's 
iterate through fifteen versions and find the smallest that still fails." 
Big difference!

Anyway, no more need to embed your grammar into a test program. Just test 
the grammar directly.

-- 
You received this message because you are subscribed to the Google Groups 
"marpa parser" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to