[#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: proc/block with return

From: Mathieu Bouchard <matju@...>
Date: 2003-08-13 00:09:29 UTC
List: ruby-core #1390
On Tue, 12 Aug 2003, Yukihiro Matsumoto wrote:

> In message "Re: proc/block with return"
>     on 03/08/12, Mathieu Bouchard <matju@sympatico.ca> writes:
> |irb(main):001:0> def f(&b) b.call; end; def g; f{return 42}+1; end; g
> |=> 43
> |irb(main):002:0> def f; yield; end; def g; f{return 42}+1; end; g
> |=> 42
> |Normally I'd call this a bug, but it seems to be intentional,
> Hmm, I too feel smell of a bug.  Let me consider.

One first mistake of mine was to assume I recalled how Ruby works wrt
this.

One second mistake was to assume "next" is a valid replacement for that,
but it's only often so, because it really has to do with "while" and not
"yield" nor Proc#call.

Now I wouldn't know how that should be fixed.

________________________________________________________________
Mathieu Bouchard                       http://artengine.ca/matju


In This Thread