> On Apr 20, 2017, at 4:06 PM, denisgolovan <denisgolo...@yandex.ru> wrote:
>
> Another example is network-related code (both client and server code).
> Break your huge finite state machines into pipeline stages via coroutines and
> it gets pretty modular, extensive and simple to reason about.
Nicely encapsulated in that statement. I’m building these big ugly state
machines inside my classes and polluting the instance variables with muck.
Coroutines would greatly clean this up and with only minimal overhead.
Regards,
Ryan Joseph
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
