> Also, here is another argument for 'thisContext process' over 'Processor
> activeProcess'.  The former will be needed when we (someday in the
> future I hope) have multiple processes running simultaneously on
> multi-processor machines.  In this case, 'Processor activeProcess' would
> be ambiguous.
> 

No, there's still a particular process that's invoking the command. 
Similarly, getpid() works fine on Posix, even with multiple CPU's.

I'm not entirely sure I hope for a multi-CPU future, because of all the
complexity it introduces into the software, but it depends on your
goals.


-Lex