Separate call stacks [DOC] Call/CC

Anthony Hannan ajh18 at cornell.edu
Fri Feb 1 18:27:01 UTC 2002


Scott A Crosby <crosby at qwes.math.cmu.edu> wrote:
> Nominally a callCC style continuation is a single unit. This would
> indicate that, for example, the code is misarchitected. You might be able
> to avoid it, for example, by always spawning doIts in a different (clean)
> process, then have some special magic that suspends the UI process
> until that one finishes (or errors).

I've made this easy in the BC version.  Just send #run to a block and it
will run in its own process while suspending the calling process.  The
calling process resumes once the block returns or is terminated like
when you quit its debugger.  If the UI process is suspended while the
debugger pops up, another UI process will be created to interact with
it, but this UI process will be terminated once the previously suspended
UI process is resumed (like in the current version).



More information about the Squeak-dev mailing list