From: Eric Mahurin <eric_mahurin@...>
Date: 2005-06-30T01:59:27+09:00
Subject: Re: yield does not take a block

--- Daniel Brockman <daniel@brockman.se> wrote:
> Eric Mahurin <eric_mahurin@yahoo.com> writes:
> 
> > I think the destructive modification of a class and of an
> object's
> > class (making its class a singleton) are the main culprits.
> 
> However, I ``destructively'' modify standard library classes
> and
> modules all the time.  This is a major selling point for
> Ruby.

I'm not going to argue that it is not useful, because it is and
I use it.  I'm just saying that being able to modify a class
and the (singleton) class of an object at runtime will prohibit
some amount of optimization within ruby.  If these were done at
compile/parse time or nondestructively (returning a new
class/object), it would be easier to optimize ruby, but
obviously less flexible.



		
____________________________________________________ 
Yahoo! Sports 
Rekindle the Rivalries. Sign up for Fantasy Football 
http://football.fantasysports.yahoo.com