From: Carlos <angus@...>
Date: 2005-04-22T06:14:08+09:00
Subject: Re: [EVALUATION] - E03e - The Ruby Object Model (Summary)

[Yukihiro Matsumoto <matz@ruby-lang.org>, 2005-04-21 17.46 CEST]
> Besides seeing no real need, such method is highly connected to the
> current implementation.  Future Ruby (or different implementation of
> Ruby interpreter) may want to choose other strategy, for example,
> creating a temporary class-like object to manipulate singleton
> methods, then update internal object structure according to that
> class-like object.  Under the implementation like this, a method to
> obtain singleton class has no meaning.

I think, in a 90% the singleton class is used for:

 * define methods for the object
 * attr
 * private
 * alias_method
 * undef and undef_method

Maybe if you provide a way to do the last four from inside instance_eval,
people would forget the singleton class...