Re: [platform-swt-dev] MacOS X port status?

["Jeff Brown" <j9brown@xxxxxxxxxxxxxxxxx>]

> Threads that don't execute concurrently?  May the Force be with you!
> See you next term.

i.e. Exactly one of a set of threads is ever unblocked and
running user code at any given time -- like a baton passing
approach.

Just for fun, I have implemented a Coroutine class that
supports both full-coroutines and semi-coroutines using
Threads that operate this way.  It's rather wasteful in the
sense that switching threads is more expensive than just
switching execution states, and simulating coroutines using
threads results in significant synchronization overhead.
Impractical, but interesting nonetheless.