Hi Ertugrul,

> Coroutines actually capture this kind of composition (where some code
> interrupts itself to hand control over to some other code) very well.
> Perhaps it would be better to use terms from that abstraction instead.
> In fact, iteratees are a special case of coroutines.

That would seem to make sense, if there is appropriate terminology.

And if we are indeed talking about co-routines, i.e. cooperation
between peers, routines of equal status, that would in itself suggest
that the X-or and X-ee names that imply an asymmetric relationship
are somewhat unfortunate choices conveying the wrong intuition.

Best,

/Henrik

--
Henrik Nilsson
School of Computer Science
The University of Nottingham
[email protected]

_______________________________________________
Haskell-Cafe mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/haskell-cafe

Reply via email to