[#1378] differences between Module and Class ? — Mathieu Bouchard <matju@...>

25 messages 2003/08/11
[#1387] Re: differences between Module and Class ? — matz@... (Yukihiro Matsumoto) 2003/08/12

Hi,

[#1442] Re: differences between Module and Class ? — Mathieu Bouchard <matju@...> 2003/08/21

[#1406] _id2ref bug? — Ryan Pavlik <rpav@...>

While debugging some caching code, I've come across a segfault related

22 messages 2003/08/14
[#1407] Re: _id2ref bug? — matz@... (Yukihiro Matsumoto) 2003/08/14

Hi,

[#1413] Re: _id2ref bug? (REPRODUCED, short) — Ryan Pavlik <rpav@...> 2003/08/14

On Fri, 15 Aug 2003 01:57:18 +0900

Re: using procs with returns result in thread error

From: matz@... (Yukihiro Matsumoto)
Date: 2003-08-29 12:14:05 UTC
List: ruby-core #1490
Hi,

In message "Re: using procs with returns result in thread error"
    on 03/08/29, Mauricio Fern疣dez <batsman.geo@yahoo.com> writes:

|> |t = proc { return 4 }
|> |
|> |Thread.new {
|> | t.
|> |}.join 
|> |
|> |results in a thread error complaining about a return
|> |statement in a thread - this complain feels wrong 
|> |to me ...  
|> 
|> Probably we need better description.  I meant "return jump can't
|> across thread".  Any suggestion?
|
|Why worry? Anyway the new semantics in 1.8 make this a non-issue.

Because it still happens if we use Proc.new instead of proc.

							matz.


In This Thread

Prev Next