Re: Back & Forth - Co-routines

minforth@gmx.net (minforth) writes:

Thanks, that makes sense. Each call to the outer function
creates a data record for (the contexts of) each of its inner
closure(s). The context records need to be managed somehow.

Most languages with closures also have garbage collection, or anyway
scope-controlled deallocation like in C++.  It may not be obvious, but
closures are sort of the same thing as OOP, just viewed from a different
angle.  Storage for the internal data of OOP instances has to be managed
in about the same way.