From: Yukihiro Matsumoto <matz@...>
Date: 2006-06-16T11:36:06+09:00
Subject: Re: Why the lack of mixing-in support for Class methods?

Hi,

In message "Re: Why the lack of mixing-in support for Class methods?"
    on Fri, 16 Jun 2006 02:01:53 +0900, transfire@gmail.com writes:

|I see. I wouldn't otherwise have a problem with the name 'funcall' but
|it's a meta-programming method and as such it's something important to
|always have available. I have BasicObject class (basically the same as
|BlankSlate) which clears out the Kernel methods. But some methods are
|too important to remove. Thankfully all the important ones (except #dup
|and #clone) start with either '__' or 'instance_' (eg. __send__). But
|#funcall will add another exception. It would be nicer to see a
|consistant pattern in the naming of these meta-methods.

Good point.  We will have __funcall__ as well.  Thank you.

							matz.