From: Jeremy Kemper <jeremy@...>
Date: 2008-04-01T10:24:13+09:00
Subject: Re: Module.new(&block) in Ruby 1.9

Hi,

On Thu, Jan 3, 2008 at 6:14 AM, SASADA Koichi <ko1@atdot.net> wrote:
>  ts wrote:
>  >>>>>> "S" == SASADA Koichi <ko1@atdot.net> writes:
>  >
>  > S> This issue is in bootstraptest/pending.rb.  I'll fix until next
>  > S> release.  On current VM structure, it's hard to fix.  So, I must
>  > S> change VM frame stack structure for this issue. sigh.
>  >
>  >  Well, I'll surely say a stupidity but, for this case, this is
>  >  iseq->cref_stack which has a problem, no ?
>  >
>  >  Why no do like blockptr with block.iseq (i.e. a copy of iseq) and change
>  >  iseq.cref_stack or do it exist some another problem ?
>
>  ah, great!  i missed "copying" iseq!
>
>  sizeof(iseq) is big, so i'll separate iseq (bytecode information)
>  and dynamic information such as cref.

Any progress on this? I checked that it's still unresolved on latest trunk.

This is the only issue blocking Rails compatibility with Ruby 1.9 :)

Best,
jeremy