On Mon, May 26, 2003 at 11:54:46AM -0700, Michael Lazzaro wrote: [ snip ] > [1.4] Cothreads > > Consider a single programmatic entity that could handle the entire > problem space described -- a single unit that represented all the most > common usages of HCCCT.
I've read this post far more times than I care to admit and I still see no merit to conflating "threads" and "coroutines". To me, the salient feature of coroutines is the ability to start from the beginning or from where we left off, while the salient feature of threads is independent simultaneous execution with (possible) data sharing. These are separate "primitive" concepts in my brain and merging them into one cothread thing just seems wrong. -Scott -- Jonathan Scott Duff [EMAIL PROTECTED]
