Hi Quenio, I can't speak for GNU Smalltalk, but yield in general is a tricky business, and does often not mean what one might think. A good way of thinking of yield is: "Hi scheduler, I'm not done yet, but if you have something important to do, I will yield now". In particular, yield MAY be a no-op, so never put it in a busy-wait loop.
Anyways, puting a delay in the main process makes the two processes take turns on the cpu. This may be a bug, a feature, or per design, I have really no idea. Just don't ever put yield in a busy-wait loop, and everyone will be fine. :-) /Tommy _______________________________________________ help-smalltalk mailing list help-smalltalk@gnu.org https://lists.gnu.org/mailman/listinfo/help-smalltalk
