Come for the quick hacks, stay for the epiphanies. | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Approaches like this work, for some definition of work, but IMO miss the point of having coroutines.
With real coroutines, you want the cooperating functions to restart with all local state intact and an unknown amount of cooperating to do. For instance you want to be able to do things like have a loop, and inside that loop yield control however many times makes sense based on the data that function sees. Your approach does not allow you to easily structure those local scopes, or to have that flexibility in how you cooperate. For a realistic example, read Coroutines in C. (I linked to it before.) Note where the emits are placed in the initial decompression routine and where the corresponding getchar is in the parsing routine. That is the kind of cooperating control structure that you want to be able to emulate. Hopefully that gives you better perspective on the problems that we'd like to be able to address. In reply to Re: Easy coroutines?
by tilly
|
|