I managed to build one on top of attoparsec's lazy parser that "seems to work" -- but I'd like ghc to flush a bit more regularly so I could test it better.
-- Don On Sun, May 1, 2011 at 7:59 PM, Bryan O'Sullivan <b...@serpentine.com> wrote: > On Thu, Apr 28, 2011 at 3:00 PM, Don Stewart <don...@gmail.com> wrote: >> >> So we'd need a lazy (or incremental) parser, that'll return a list of >> successful event parses, then block. I suspect this mode would be >> supported. > > A while ago, I hacked something together on top of the current eventlog > parser that would consume an event at a time, and record the seek offset of > each successful parse. If parsing failed (due to unflushed data), it would > try again later. I think I might even claim that this is a somewhat sensible > and parsimonious approach, but I'm drinking wine right now, so my judgment > might be impaired. _______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users