Ruby Issue Tracking System

06/11/2010

05:40 PM Ruby Bug #3420: Module#method calling <=> causes SystemStackError

=begin
Please let me ask, why as from 1.9.2:


Sat Oct 24 13:38:45 2009 Yukihiro Matsumoto

* object.c (rb_obj_cmp): defines Object#<=>. [ruby-core:24063]

Before that all ruby implementations did:

ruby-1.8.7-p249 >
Brok... boof (Florian Aßmann)

08:30 AM Ruby Bug #3420: Module#method calling <=> causes SystemStackError

=begin
Ok, but then imho the Exception is inappropriate and most people don't expect a SystemStackError when they found a method implementation missing. For most people it isn't obvious (see commit message in the ref link) why including... boof (Florian Aßmann)

06/10/2010

04:12 PM Ruby Bug #3420: Module#method calling <=> causes SystemStackError

=begin
Sorry again, this should be in ruby-1.9... :/
=end
boof (Florian Aßmann)

04:03 PM Ruby Bug #3420: Module#method calling <=> causes SystemStackError

=begin
Sorry, ruby -v: ruby 1.9.2dev (2010-06-01 revision 28116) [x86_64-darwin10.3.0]
=end
boof (Florian Aßmann)

03:53 PM Ruby Bug #3420 (Rejected): Module#method calling <=> causes SystemStackError

=begin
It seems the SystemStackError will be raised when compar.c calls the spaceship:

static VALUE
cmp_eq(VALUE *a)
{
VALUE c = rb_funcall(a[0], cmp, 1, a[1]);
...

ruby-1.9.2-head >
... boof (Florian Aßmann)