Calling lexeme_alternative() twice should work, and I believe it's a technique used in an app or two. RNS pointed to the location of some examples in this thread: https://groups.google.com/forum/#!topic/marpa-parser/X2DLX8q6Byw
On Mon, Jul 20, 2015 at 8:26 AM, Thomas Weigert <[email protected]> wrote: > I am trying to figure out how I can create, from within an external > scanner, an ambiguous parse. What I want to achieve is this: I get fed an > event from marpa, and now in the code handling this event I will need to > recognize the matched symbol as two different lexemes, each causing a > different parse to result. > > From the documentation it seems that I could call lexeme_alternative() > twice, once for each lexeme I want to create. But, alas.... > > Could you please point me to an example where somebody has successfully > done something like this? > > In summary, I hope to, in a pause look at the expected symbols. If I find > that certain symbols are expected, create a parse for each of them, > resulting in a parse forest. (In fact, I know already that one of the > alternatives will die later, but at this point, I do not yet know which.) > > Thanks, Th. > > -- > 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.
