[#25936] [Bug:1.9] [rubygems] $LOAD_PATH includes bin directory — Nobuyoshi Nakada <nobu@...>

Hi,

10 messages 2009/10/05

[#25943] Disabling tainting — Tony Arcieri <tony@...>

Would it make sense to have a flag passed to the interpreter on startup that

16 messages 2009/10/05

[#26028] [Bug #2189] Math.atanh(1) & Math.atanh(-1) should not raise an error — Marc-Andre Lafortune <redmine@...>

Bug #2189: Math.atanh(1) & Math.atanh(-1) should not raise an error

14 messages 2009/10/10

[#26222] [Bug #2250] IO::for_fd() objects' finalization dangerously closes underlying fds — Mike Pomraning <redmine@...>

Bug #2250: IO::for_fd() objects' finalization dangerously closes underlying fds

11 messages 2009/10/22

[#26244] [Bug #2258] Kernel#require inside rb_require() inside rb_protect() inside SysV context fails — Suraj Kurapati <redmine@...>

Bug #2258: Kernel#require inside rb_require() inside rb_protect() inside SysV context fails

24 messages 2009/10/22

[#26361] [Feature #2294] [PATCH] ruby_bind_stack() to embed Ruby in coroutine — Suraj Kurapati <redmine@...>

Feature #2294: [PATCH] ruby_bind_stack() to embed Ruby in coroutine

42 messages 2009/10/27

[#26371] [Bug #2295] segmentation faults — tomer doron <redmine@...>

Bug #2295: segmentation faults

16 messages 2009/10/27

[ruby-core:26145] Re: A challenge: Enumerator#next in JRuby - yeild next

From: Charles Oliver Nutter <headius@...>
Date: 2009-10-17 20:47:05 UTC
List: ruby-core #26145
On Fri, Sep 25, 2009 at 9:46 PM, Tomas Matousek
<Tomas.Matousek@microsoft.com> wrote:
> I meant that "yield next" would only transform the method (or block) that lexically encloses it. Like in Python. If we wanted to propagate the state transformation across methods we could also introduce "yield foreach" construct [1].
>
> [1] http://citeseer.ist.psu.edu/cache/papers/cs2/355/http:zSzzSzwww.cs.kuleuven.ac.bezSz~frankzSzPAPERSzSzFTfJP2005.pdf/iterators-revisited-proof-rules.pdf

This is definitely an option but it requires us to either transform
all methods that have such a yield (perhaps not a big deal; Jython
does this) or be able to inspect the target method to see if it could
be lazily transformed.

I'm leaning more and more toward the opinion that MRI-style
Enumerator#next is not going to be supportable on many other
implementations, and the explicit iteration protocol is the way to go.

- Charlie

In This Thread

Prev Next