> what is the purpose of a ".CoRoutine"? How does that differ from having
> Rexx methods execute concurrently?
>
Excerpt from
http://ssw.jku.at/Research/Papers/Stadler11Master/Stadler11Master.pdf
<<
Producer/consumer problems can often be implemented elegantly with
coroutines.
Coroutines also provide an easy way to inverse recursive algorithms into
iterative ones.
Coroutines are non-preemptive light-weight processes. Their advantage over
threads is that they do not have to be synchronized because they pass
control to each other explicitly and deterministically.
>>
Of course, it's possible to emulate coroutines with threads, this is what I
do with .Coactivity. But this is not a good choice for performances. A
possible "real" implementation would be to use fibers, but that's more
ambitious.
>
> What does one need to know to decide whether to use a CoRoutine or not?
>
See http://www.dabeaz.com/coroutines/Coroutines.pdf
This is about Python but the use cases are interesting.
Jean-Louis
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
