[squeak-dev] Please try out | Fixes for debugger invocation during code simulation

Jaromir Matas m at jaromir.net
Sat Mar 13 20:30:09 UTC 2021


Hi Marcel, Christoph,

trying to follow this wonderful job, thanks indeed :) A question: How is the
genuine process supposed to answer #isTerminated, isActive etc.? At the
moment it answers true to isTerminated if the effective process variable is
set. As a consequence the genuine process is not shown on the Process
Browser in such a case. 

<http://forum.world.st/file/t372955/active_genuine_effective.png> 

The effective process rightly answers true to isActiveProcess but what about
the genuine one?

Generally there's not much difference between a genuine and a terminated
process. Both have suspendedContext = nil. I guess the only difference is
that the genuine process is not terminated, and Processor is the place
keeping this information.

Should there be two active processes? The genuine and the effective? And
extend the isActiveProcess like

	self == Processor activeProcess or: [self effectiveProcess == Processor
activeProcess]

Thanks again, I hope I'm not confused again :)




-----
^[^ Jaromir
--
Sent from: http://forum.world.st/Squeak-Dev-f45488.html


More information about the Squeak-dev mailing list