>
> > All you would need to add to OMeta in order to support "streamed
> > output" (if I haven't completely misunderstood your question) is a
> > new kind of semantic action that adds a new value to the end of the
> > output stream.
>
> Thanks, you described exactly what I'm looking for.
I'm not sure that what I've described completely solves your problem. The
part that's missing is that if you want this to work well with concurrency,
then you'll need a really good story for how the "corrections" that are made
to the output stream (that happen upon backtracking) won't mess up the next
parser/matcher on the pipeline. But I think that can be worked out with some
careful thinking.
Cheers,
Alex
>
> > p.s. I think that one of Ian's parser frameworks had / has support
> > for "streamed output", but I don't know any details, so it may or
> > may not work in the way I've described here.
>
> jolt2.5 (some files that Ian sent me) had an invoke rule ("<RULE>")
> to execute another parser and parse its output, but it wasn't done
> asynchronously, and the relationship between the parsers was fixed at
> grammar definition time. He may have done something other than that,
> but that's the closest I've seen to streaming.
>
> --
> Michael FIG <[email protected]> //\
> http://michael.fig.org/ \//
>
> _______________________________________________
> fonc mailing list
> [email protected]
> http://vpri.org/mailman/listinfo/fonc
>
_______________________________________________
fonc mailing list
[email protected]
http://vpri.org/mailman/listinfo/fonc
