Hi --

On Fri, 13 Dec 2002, Chris Pine wrote:

> True, this isn't a problem if you don't allow Class to be subclassed;
> Class.new is only broken if you remove the checks which prevent you from
> noticing it's broken... er, so to speak.

Or, to put it another way: it isn't broken :-) It's part of a system,
and it does exactly what it needs to in that system.  Only if objects
other than Class had access to Class.new would it matter what happened
when they called it.

I have a sort of branched-off thought related to all of this.  It's
the thought of inducing a class from an object.  I kind of think
that's what you're getting at when you talk about making an object's
singleton class a real class.  My problem with that is that I think
having the singleton class itself makes sense.  But, if I'm correctly
abstracting your underlying idea, I can imagine (at least
theoretically) that it might be good to be able to sort of take a
snapshot of an object's behavior and capture it in/as a class.

At some point I may even try my hand at this.  Sauve qui peut.... :-)


David

-- 
David Alan Black
home: dblack / candle.superlink.net
work: blackdav / shu.edu
Web:  http://pirate.shu.edu/~blackdav