On Tuesday, 10 February 2015 14:24:56 UTC+11, Thomas Weigert wrote: > > Thanks, Ron. > > I see how the Ruby Slippers can work if you know ahead of time what the > text will be that we need to insert into the input, so we can "secret it > away" before calling read. I guess I could get this to work by prescanning > the input for all the text strings, then putting them all into "Ruby > Slippers Shoeboxes" at the end of the input string and when hitting one of > these tokens doing the Ruby Slipper thing, just like you did in > match.parentheses.02.pl >
But that prescanning is just what we want Marpa to do! Hmmm. The 4 points in your first post are incredibly restrictive. I suggest you revisit that topic. For example, if they are all prefixed with #, then life is simple(r). If they all end with \n, then that helps too. I still think the only way to handle a lot of flexibility in such introns (to use DNA-style terminology) is to accept that you'll have to write the grammar for all such cases. We can help you simplify it, but ATM it seems far too vague (in the nicest possible way, of course :-) to work with. -- 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.
