Hi,

In message "[ruby-talk:12382] Thread::parent ?"
    on 01/03/11, Eric Sven Ristad <ristad / mnemonic.com> writes:

|What's the cleanest way to for a thread to access it's parent (ie.,
|the thread that created it), other than for the parent to pass itself
|as an argument to Thread.new, eg.,
|
|    t = Thread.new(Thread::current){|parent|  ... }
|
|If there's no cleaner way, then it might be nice to define a new
|Thread class method Thread::parent that does that.

All threads are created equal (except the "main" thread), so that
there's no such thing like parent thread.  The implementation does not
preserve the information of the creating thread.

Do you think it's really worthy to add new slot to the internal
structure to preserve this information, making things bit complex,
to allow you avoid passing current thread information?

							matz.