[#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

proc/block with return

From: Mathieu Bouchard <matju@...>
Date: 2003-08-11 20:03:31 UTC
List: ruby-core #1381
it seems that the semantics of return inside of a proc/block have changed
in subtle ways, but I can't really figure out what's going on.

I've seen it listed in http://dev.faeriemud.org/changes-1.8.0.html, but I
have trouble understanding what happened. I've looked a bit into
ChangeLog, like this:

grep -n5i return doc/ChangeLog-1.8.0 |grep -i proc

and found an entry like this:

Fri Jun 20 23:28:27 2003  Yukihiro Matsumoto  <matz@ruby-lang.org>

        * eval.c (proc_invoke): should not propagate TAG_BREAK and
          TAG_RETURN from orphan Proc object. [ruby-core:01148]



But I will please need some help to figure out the consequences of the
above log entry. I would like examples of how ruby 1.8 is different from
1.6, and what are similarly constructed cases that are _not_ different
from 1.6, so that I can have a precise idea of the change.

A pointer to sufficiently detailed documentation would be helpful too.

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


In This Thread

Prev Next