From: transfire@...
Date: 2006-06-08T22:08:04+09:00
Subject: Re: Why the lack of mixing-in support for Class methods?


ara.t.how...@noaa.gov wrote:

> module M
>    def self.new
>      'yikes!'
>    end
>    def self.alloc
>      'even worse'
>    end
>    def self.name
>      'this is getting bad'
>    end
>    def self.is_a?
>      'i hope you did not override this'
>    end
> end
>
> class C
>    include M
> end

Sigh. We've been through this Ara. It's a silly example --don't use
those methods if you don;t want to override them --and what if you do?

Nonethesless, I agree with Matz. I think a simple alternative call is
the prefect compromising solution. Perhaps:

 class C
    inherit M
 end

Also, This post is kind of timely, I'be been preparing a post with
example's from Nitro on the extensive need of this behavior --you
should see the many "hacks" being used to accomplish this there --I
think at least three different techinqes are being used throughout
dozens of components.

T.