< :the previous in number  ^ :the list in numerical order  > :the next in number  P :the previous (in thread)  N :the next (in thread) |<:the top of this thread >|:the next thread  ^ :the parent (reply-to) _:the child (an article replying to this) >:the elder article having the same parent <:the youger article having the same parent ---:split window and show thread lists  | :split window (vertically) and show thread lists  ~ :close the thread frame .:the index ..:the index of indices

Subject: Re: Threads preventing garbage collection?
From: Brian Candler <b.candler@ b . m
Date: Thu, 18 Sep 2008 06:24:04 +0900
References: 315125 315139 315142 315149 315150 315151 315164 315177
In-reply-to: 315177

> 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/.