Re: Experimental PATCH to improve thread performance

On Thu, Dec 27, 2007 at 01:57:22AM +0900, Charles Oliver Nutter wrote:
> Except that requiring users to use synchronization points in order to make 
> a feature safe basically means everyone will do it the unsafe way. 
What I meant was in the same line of though than Brent's: only act upon
queued exceptions if the thread is inside a synchronization point. That
way, the exception mechanism, without being completely safe, is reduced
to cases where it can be safe. Ensuring that the child thread is able to
understand the exception is another matter altogether: it is the
responsibility of the program designer.


> a clear checkpoint and agreement from both parent and child thread that 
> it's ok to raise, you can't *ever* know that a thread is safe to raise in,
Threads are never created out of the void. Threads are created by the
program itself and multi-thread messaging is part of the design of the
whole program. Inter-thread exceptions are a flexible inter-thread error
messaging and I certainly think that removing them altogether would
remove a nice idea from the Ruby language.
-- 
Sylvain