This discussion seems to have died out.  Is this something which
should/will be fixed.  Should I open a bug ticket?

On Thu, Aug 27, 2009 at 12:53 PM, Yusuke ENDOH <mame / tsg.ne.jp> wrote:
> Hi,
>
> 2009/8/27 Rick DeNatale <rick.denatale / gmail.com>:
>> On Wed, Aug 26, 2009 at 7:25 PM, Yukihiro Matsumoto<matz / ruby-lang.org> wrote:
>>> Hi,
>>>
>>> In message "Re: [ruby-core:25143] Is this an intentional change in 1.9?"
>>>         >>>
>>> |This seems like a 1.9 bug. Is it?
>>>
>>> I vaguely remember ko1 explained me about the change due to a YARV
>>> internal issue.        
>>
>> I think it's a code generation issue, and also that it's important not
>> to change the semantics of a.x ||= value
>
>
> I agree.           ᮽ> but 1.9 cheated on me.
>
>
>   
>     >  >
>  ¨ セ 
>  ¨  
>
>
> Here is a patch.     
> are executed than current implementation.     
> impact of speed.
>
>
> Index: compile.c
> ===================================================================
> --- compile.c (revision 24684)
> +++ compile.c (working copy)
> @@ -3842,22 +3842,26 @@
>   >   >   > - send a= # v
> - jump lfin # v
> + swap  v r
> + topn 1  v r v
> + send a= # v ?
> + jump lfin # v ?
>
>   >   > +
> + lfin: # o ?
>   >
> - lfin: # v
> -
>  and
>   >  >   >   > - send a= # v
> - jump lfin # v
> + swap  v r
> + topn 1  v r v
> + send a= # v ?
> + jump lfin # v ?
>
>  others
>   > @@ -3881,15 +3885,17 @@
>  
>  Ψ 婬 >  Ũβ 孾婻
> + ADD_INSN(ret, nd_line(node), swap);
> + ADD_INSN1(ret, nd_line(node), topn, INT2FIX(1));
>  Ĩ 婬 IJͨ孾䩬
> INT2FIX(1));
>  ̨婬 
>
>  ̨>  Ψ 婬 
> - ADD_INSN(ret, nd_line(node), pop);
>
>  ̨
> + ADD_INSN(ret, nd_line(node), pop);
>  
>  >  Ũβ 孾婻
>
> --
> Yusuke ENDOH <mame / tsg.ne.jp>
>
>



-- 
Rick DeNatale

Blog: http://talklikeaduck.denhaven2.com/
Twitter: http://twitter.com/RickDeNatale
WWR: http://www.workingwithrails.com/person/9021-rick-denatale
LinkedIn: http://www.linkedin.com/in/rickdenatale