[#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: matz@... (Yukihiro Matsumoto)
Date: 2003-08-13 17:43:52 UTC
List: ruby-core #1403
Hi,

In message "Re: proc/block with return"
    on 03/08/13, george.marrows@ps.ge.com <george.marrows@ps.ge.com> writes:

|Here's another return/proc/block oddity, though it may just be a side effect
|of the above. 
|
|If you run the code below on 1.8.0 you get:
|trace: [1, 4, 6, 8, 2]
|
|but if you make the suggested '&p' -> 'p' changes, you get:
|trace: [1, 4, 6, 8, 2, 5]
|
|So the behaviour of return depends on the history of how the block got to
|the yielding method, which is odd.

It's odd indeed.  Let me check.

							matz.

In This Thread

Prev Next