[#3726] Fixnum#clone and Float#clone raise different exceptions — "David A. Black" <dblack@...>

Hi --

15 messages 2004/11/12
[#3749] Re: Fixnum#clone and Float#clone raise different exceptions — "David A. Black" <dblack@...> 2004/11/16

Hi --

[#3751] Re: Fixnum#clone and Float#clone raise different exceptions — Yukihiro Matsumoto <matz@...> 2004/11/16

Hi,

[#3752] Re: Fixnum#clone and Float#clone raise different exceptions — "David A. Black" <dblack@...> 2004/11/16

Hi --

[#3785] The latest 1.8.2 cvs prints parse error when starting extension compiling — Yukihiro Matsumoto <matz@...>

Hi,

13 messages 2004/11/23
[#3787] Re: The latest 1.8.2 cvs prints parse error when starting extension compiling — Johan Holmberg <holmberg@...> 2004/11/23

Re: Ruby 1.8.2 preview3

From: Yukihiro Matsumoto <matz@...>
Date: 2004-11-08 04:44:48 UTC
List: ruby-core #3697
Hi,

In message "Re: Ruby 1.8.2 preview3"
    on Mon, 8 Nov 2004 13:41:29 +0900, Yukihiro Matsumoto <matz@ruby-lang.org> writes:

||Assigning nil to an array slice in Array#[]= no longer deletes the
||elements from the array.  Is this change intended?
|
|No.

Oops, I meant yes.  I.e. the CVS head (1.9) no longer deletes the
elements by nil.  It's intentional.  1.8.2 still keeps old behavior
that deletes elements with nil.

							matz.

In This Thread