From: Trans <transfire@...>
Date: 2008-12-05T20:24:13+09:00
Subject: [ruby-core:20367] Re: Leave my open classes alone (was Behavior: autoload calls 	rb_require() directly)



On Dec 5, 1:36�am, "Bill Kelly" <bi...@cts.com> wrote:
> From: "Jeremy McAnally" <jeremymcana...@gmail.com>
>
>
>
> > Soooo basically you're advocating a Python-like object tree, which is
> > the single trait about Python's language features that makes me burn
> > with rage.
>
> I think, rather, that Trans was wanting Ruby to be just as open as it
> currently is,

Yes. And hopefully even more open. I've written code were I wanted to
redefine ||, &&, !, etc, within special contexts.

> but he was looking for a way to quickly detect whether
> any crucial class methods have been overridden, that could be used
> behind the scenes to make decisions about optimization.

Precisely. My thinking-out-load was that the isolation of core static
code into "Kernels" made a useful delineation for easily determining
optimizations:

  optimize_methods = Fixnum::Kernel.instance_methods(false) -
Fixnum.instance_methods(false)

And overrides more elegantly written:

  class Fixnum
    def +(a,b)
      puts "adding"
      super
    end
  end

T.