> but threads *do* hold their context

Could you define "context" in this, erm, context? :-)

I thought that 'def' started a new scope/context. If a thread is started 
from within def, how could it know about objects which are only 
referenced from outside that scope?

It's as if the thread is holding on to bits of stack or bindings which 
really belong to another thread.
-- 
Posted via http://www.ruby-forum.com/.