From: Chris Roos <chrisjroos@...>
Date: 2006-09-16T20:13:15+09:00
Subject: Re: Ruby keywords vs methods

On 9/16/06, Pit Capitain <pit@capitain.de> wrote:
> Chris Roos schrieb:
> > It'd be nice if, on redefining an existing method, we could get a
> > warning to allow us a quicker route to the problem.
>
> Chris, just call Ruby with the -w command line option. With your example
>
>    class Foo
>      def foo
>        p 'foo'
>      end
>    end
>
>    class Foo
>      def foo
>        p 'new foo'
>      end
>    end
>
> I get
>
>    warning: method redefined; discarding old foo
>
> Regards,
> Pit
>
>
Ok, so this is being pedantic, but that doesn't appear to work if you
have two separate files, each defining Foo#foo, both being required by
another script.

Although I am interested in solutions to this 'problem', I'd still
love feedback on the decision of adding keywords to the language.
Maybe I should break that to another thread with a better subject (any
suggestions)?

Cheers,

Chris