[#11439] comments needed for Random class — "NAKAMURA, Hiroshi" <nakahiro@...>

-----BEGIN PGP SIGNED MESSAGE-----

15 messages 2007/06/12

[#11450] Re: new method dispatch rule (matz' proposal) — David Flanagan <david@...>

This is a late response to the very long thread that started back in

17 messages 2007/06/13

[#11482] Ruby Changes Its Mind About Non-Word Characters — James Edward Gray II <james@...>

Does this look like a bug to anyone else?

10 messages 2007/06/16

[#11505] Question about the patchlevel release cycle — Sylvain Joyeux <sylvain.joyeux@...4x.org>

1.8.6 thread support was broken in bad ways. It stayed for three months

20 messages 2007/06/20
[#11512] Re: Question about the patchlevel release cycle — Urabe Shyouhei <shyouhei@...> 2007/06/20

Hi, I'm the 1.8.6 branch manager.

[#11543] Re: Apple reportedly to ship with ruby 1.8.6-p36 unless informed what to patch — James Edward Gray II <james@...>

On Jun 27, 2007, at 4:47 PM, Bill Kelly wrote:

10 messages 2007/06/27

Re: new method dispatch rule (matz' proposal)

From: Daniel Berger <Daniel.Berger@...>
Date: 2007-06-14 15:52:37 UTC
List: ruby-core #11459
Rick DeNatale wrote:

<snip>

> My opinion is that the cure for this 'problem' is worse than the disease.

I'd settle for a warning when run with -w. This code emits a warning 
when run with -w:

# redef.rb
class Foo
    def bar
       puts "hello"
    end

    def bar
       puts "world"
    end
end

redef.rb:6: warning: method redefined; discarding old bar

But this does not:

# redef2.rb
class Foo
    def bar
       puts "hello"
    end
end

class Baz < Foo
    def bar
       puts "world"
    end
end

Is there any way to make the 2nd case emit a warning without major 
changes to core Ruby?

Dan

In This Thread