Re: Self-scheduling threading
Re: Self-scheduling threading
- Subject: Re: Self-scheduling threading
- From: Bob Ippolito <email@hidden>
- Date: Wed, 16 Mar 2005 23:26:37 -0500
On Mar 16, 2005, at 22:28, Scott Ribe wrote:
Somehow this approach seems simpler to
me than beating on the stack with memcpy :) :) Man that technique
freaks me. Maybe it works but... so gross! And I'd be extremely
concerned about using it in production code. Memcpy'ing over the
currently live stack just doesn't seem safe.
Yeah, I think a true need for coroutines is kind of unlikely to ever
crop up
on the Cocoa list. FYI I found this when searching for a solution to
some
simulation modeling, where an obvious and conceptually easy approach
would
involve a thread per component modeled. The problem though is that
it's not
practical to run 100,000 threads in a process ;-) And there were other
issues involving encapsulation of state and simplicity of expressing
the
component calculations, that led to a need for coroutines. Fairly
exotic
stuff.
You rarely ever *need* coroutines.. you could get away with just using
continuation passing style, probably plus NSInvocations or something.
-bob
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden