That last one is much better.�� I really like the presentation of the "newProcess" method.�� Its a quick technical dive.�� Perhaps the comment needs to be tuned a wider audience,describing how process creation is green-thread and and all managed by Smalltalk code.�� The warning about debugging this deep does't need to be shown.�� This is "marketing" after all.��
it might also be good if the comment described what class "self" is referring to, and what sending value to it does.
Change "Simulation guard" to "VM simulation guard primitive".�� Also breaking the code down to use a variable I think makes it clearer for an outside to parse.
I wonder if the method text might something like be...
newProcess
"The receiver (self) of this message is a closure. ����
�� �� �� �� �� �� Return a Process (green thread) to evaluate the value of receiver's bytecode.
�� �� �� �� �� �� The process is not scheduled."
<primitive: 19> "VM simulation guard primitive"
|executionContext|
executionContext := [self value. Processor terminateActive] asContext.
^ Process
forContext: executionContext��
priority: Processor activePriority
Try masking around the "newProcess" window on a separate layer so the whole window is "brought forward".��