Hi Daniel, it helps (at times) to work the other way round—code to doc, e.g., re actions, start from a simple example <https://github.com/jeffreykegler/Marpa--R2/blob/master/cpan/t/sl_topsyn.t> and read the doc <http://search.cpan.org/~jkegl/Marpa-R2-3.000000/pod/Semantics.pod> to clarify/elaborate.
Another way is that Marpa can produce a parse value as an abstract syntax tree (ast) (article <http://jeffreykegler.github.io/Ocean-of-Awareness-blog/individual/2013/03/bnf_to_ast.html> , code <https://gist.github.com/jeffreykegler/4747725>) that you can traverse recursively, as, e.g., in this simple but functional json parser <https://github.com/jeffreykegler/Marpa--R2/blob/master/cpan/t/sl_json_ast.t> . On Mon, Mar 13, 2017 at 4:59 PM, Daniel Blanch < [email protected]> wrote: > Hi Marpers, > > I've been using Marpa for a while, it seems promising, but I find it > difficult to understand how default actions and custom actions work > together when trying to get a result. Where can I find a tutorial or > documentation to understand it? How did you learn Marpa? Documentation is a > bit confusing. > > Thank you very much in advance. > > Regards. > > Daniel. > > -- > 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.
