Some time ago I worked on the base[1] from which I could built this on top of. My plan was to take simple rule descriptions [2] and generate the code needed to configure the parser. There are quite a few experiments in this repository that take different approaches to structure the output. Maybe this could be of some help to someone building C code from SLIF descriptions.
[1]: https://github.com/pstuifzand/marpa-cpp-rules/ [2]: https://github.com/pstuifzand/marpa-cpp-rules/blob/master/rules.txt -- Peter Stuifzand | peterstuifzand.nl | @pstuifzand <http://twitter.com/pstuifzand> On Wed, Jan 28, 2015 at 1:58 AM, Jeffrey Kegler < [email protected]> wrote: > I forgot to add, and should -- if you happen to look into the SLIF's > mixed C/Perl code, my apologies. It "evolved" over time and is very > hard to read. > > -- > 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. > -- 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.
