Henning Thielemann wrote:
> I have put essentially Oleg's explanation to the Wiki:
> http://haskell.org/haskellwiki/Enumerator_and_iteratee
The examples given are not really illustrative of how we
approach parsing with failure or I/O with media failure using
the Iteratee/Enumerator approach
Jason Dusek schrieb:
> Henning Thielemann wrote:
>> Jason Dusek schrieb:
>>> I'm taking a stab at composable streams, starting with
>>> cursors. I managed to make a derived cursor today -- as I
>>> work through this stuff, I hope to understand
>>> Iteratee/Enumerator better.
>> How about a wiki pa
Henning Thielemann wrote:
> Jason Dusek schrieb:
> > I'm taking a stab at composable streams, starting with
> > cursors. I managed to make a derived cursor today -- as I
> > work through this stuff, I hope to understand
> > Iteratee/Enumerator better.
>
> How about a wiki page on the roles of enum
Jason Dusek schrieb:
> I'm taking a stab at composable streams, starting with
> cursors. I managed to make a derived cursor today -- as I work
> through this stuff, I hope to understand Iteratee/Enumerator
> better.
How about a wiki page on the roles of enumerators and iteratees, best
expl
I'm taking a stab at composable streams, starting with
cursors. I managed to make a derived cursor today -- as I work
through this stuff, I hope to understand Iteratee/Enumerator
better.
--
Jason Dusek
http://github.com/jsnx/streams/tree/554dd69339f027f113a6cfa16f552727ba9d92b3/Control/St
Hi Jason!
2008/12/22 Jason Dusek :
> So an iteratee is not like a cursor because it does not "own"
> the collection -- it just tells us how to step it. The
> enumerator "owns" the collection and provides a way to scope
> resource use?
Iteratee does not know anything about resources,
it doesn'
So an iteratee is not like a cursor because it does not "own"
the collection -- it just tells us how to step it. The
enumerator "owns" the collection and provides a way to scope
resource use?
--
Jason Dusek
___
Haskell-Cafe mailing list
Haskell-C
Hi Jason,
2008/12/20 Jason Dusek :
> So, it looks Iteratee takes a "step" on the resource --
> whatever it is -- and Enumerator manages the resource and
> sequences the steps of the Iteratee. The Enumerator, then,
> defines our way of managing a particular resource -- how to
> take a step, ho
So, it looks Iteratee takes a "step" on the resource --
whatever it is -- and Enumerator manages the resource and
sequences the steps of the Iteratee. The Enumerator, then,
defines our way of managing a particular resource -- how to
take a step, how to close it, &c. -- while the Iteratee
