From: Yukihiro Matsumoto <matz@...>
Date: 2012-02-13T10:03:48+09:00
Subject: [ruby-core:42519] Re: [ruby-trunk - Feature #5979][Open] deprecate Thread#raise

Hi,

Although I admit Thread#raise is dangerous, it's not more dangerous
than other asynchronous events, like signals.  And I don't think MRI
cannot remove signals, especially keyboard interrupts, as a real-world
language.  So there's no reason to deprecate Thread#raise, despite the
fact we need to reimplement Timeout etc.

							matz.

In message "Re: [ruby-core:42416] [ruby-trunk - Feature #5979][Open] deprecate Thread#raise"
    on Wed, 8 Feb 2012 05:44:00 +0900, Roger Pack <rogerpack2005@gmail.com> writes:

|as discussed in ruby-core, we should probably deprecate Thread#raise since it's dangerous.
|http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/42318