From: matz@... (Yukihiro Matsumoto)
Date: 2001-10-27T07:16:27+09:00
Subject: [ruby-talk:23549] Re: class Foo does not call Class.new?

Hi,

In message "[ruby-talk:23392] Re: class Foo does not call Class.new?"
    on 01/10/26, Brian Marick <marick@visibleworkings.com> writes:

|At 04:32 PM 10/25/01, you wrote:
|>No.  But in 1.7.1, I defined something I call "allocation framework",
|>which is
|>
|>   * basically, no "new" overriding (that allows your Class#new trick
|>     work in many cases).
|>
|>   * instance allocation is done by "allocation" method of the class,
|>     for example, Array#allocation for arrays.
|>
|>   * there's a few exceptions remain, for example Class does not call
|>     "allocation".
|
|I'm afraid I don't understand. Will I be able to do metaclass tricks?

First of all, I should have put "FYI" before the note.  You can't do
your trick for classes yet.  And probably you will be able to do it in
the future.

It is my only concern that making class statements syntax sugar for
Class.new might be too easy to screw up.  I may be worrying for no
reason.
							matz.