[#18121] [Ruby 1.8.7 - Bug #405] (Open) ssl.rb:31: [BUG] Bus Error — Anonymous <redmine@...>

Issue #405 has been reported by Anonymous.

14 messages 2008/08/04

[#18130] Re: New array methods cycle, choice, shuffle (plus bug in cycle) — Brian Candler <B.Candler@...>

> Seriously though... Array.first is a noun.

10 messages 2008/08/05

[#18319] NEW Command: absolute_path() -- — "C.E. Thornton" <admin@...>

Core,

14 messages 2008/08/16
[#18321] Re: NEW Command: absolute_path() -- — Yukihiro Matsumoto <matz@...> 2008/08/18

Hi,

[#18381] [Bug #496] DRb.start_service(nil) is very slow — Hongli Lai <redmine@...>

Bug #496: DRb.start_service(nil) is very slow

11 messages 2008/08/25

[ruby-core:18182] Re: [Ruby 1.8 - Bug #252] Array#sort doesn't respect overridden <=>

From: Yukihiro Matsumoto <matz@...>
Date: 2008-08-07 22:41:27 UTC
List: ruby-core #18182
Hi,

In message "Re: [ruby-core:18124] Re: [Ruby 1.8 - Bug #252] Array#sort doesn't respect overridden <=>"
    on Tue, 5 Aug 2008 04:49:27 +0900, Charles Oliver Nutter <charles.nutter@sun.com> writes:

|So this is going to be a behavioral change now? My reading of the patch 
|tells me it's now checking to see if <=> has been overridden and if so 
|using the path that actually calls it. As Ryan pointed out, this would 
|be new behavior. Can we get an official ruling on what is correct in 1.8 
|and 1.9.x?

We are not going to change 1.8 semantic in the near future.  We should
keep compatibility, even when it's inconsistent, as long as it's not
"wrong".

For 1.9, I think it's better to adopt the new behavior.  What do you
think?

							matz.

In This Thread