An idea on multithreading implementation

[Bob Sneidar]

Do you mean like when the race track is really muddy but they run the horses anyway?

Actually, you could be on to something, with the caveat that the processes would be isolated from each other. I am thinking that you could still have one stack get information about some field in another stack while that stack was doing some long drawn out task. 

I dunno, maybe it's a non starter. 

Bob


On Jan 18, 2011, at 5:09 PM, Richard Gaskin wrote:

> Sure, it's a bit of a kludge, but would be dirt-simple to implement, and wouldn't expose the treachery of race conditions to the masses. :)