conal:
>
>Lovely!
>
>Perhaps a stylistic shift would encourage writing this sort
>of elegant, fusion-friendly code.
>-- Generalized version of "interact". Encapsulates data
>getter & putter.
>genInteract :: IO i -> (o -> IO ()) -> ((i -> o) -> IO
>())
>
Lovely!
Perhaps a stylistic shift would encourage writing this sort of elegant,
fusion-friendly code.
-- Generalized version of "interact". Encapsulates data getter &
putter.
genInteract :: IO i -> (o -> IO ()) -> ((i -> o) -> IO ())
genInteract get put = \ f -> get >>= put . f
The in
Hello Donald,
Friday, June 8, 2007, 5:42:41 AM, you wrote:
> Previous experience[1] indicates it is pretty hard to write a C line
> parsing program[2] that that run this fast. And the code, with comments:
[2] uses gets() function while your haskell code read whole buffer
each time. that is the
dons:
> dons:
> > mdanish:
> > > Hello,
> > >
> > > I've been playing with the INTEST problem on SPOJ which demonstrates
> > > the ability to write a program which processes large quantities of
> > > input data. http://www.spoj.pl/problems/INTEST/
> >
> > > But when I make a slight modificatio
dons:
> mdanish:
> > Hello,
> >
> > I've been playing with the INTEST problem on SPOJ which demonstrates
> > the ability to write a program which processes large quantities of
> > input data. http://www.spoj.pl/problems/INTEST/
>
> > But when I make a slight modification, the program chews up
mdanish:
> Hello,
>
> I've been playing with the INTEST problem on SPOJ which demonstrates
> the ability to write a program which processes large quantities of
> input data. http://www.spoj.pl/problems/INTEST/
> But when I make a slight modification, the program chews up a ton more memory
> an
