Re: [ruby-cvs:18323] ruby: * eval.c (splat_value): use "to_splat" instead of "to_ary" to

On Sun, 8 Oct 2006, Yukihiro Matsumoto wrote:

> Every language grows in more recent version, as Ruby does, and PL/I did, 
> until it grows too much to collapse into a black hole by its own 
> gravity.  It's kind a like destiny.  Otherwise the language will die.

And when it finally collapses into a black hole, it dies as well, unless 
you think of the black hole as some kind of afterlife. (but I don't think 
that trapping matter and emitting blackbody X-rays is your idea of an 
afterlife)

> For people who don't like growing languages,

I'm all for languages that grow, but I'm not approving of every way in 
which they do. I favour ways that involve refactoring all along.

> I just allowed objects to respond the order "splat me" in its own 
> manner.

There's no reason to allow objects to be splatted in the way that they 
like.

> Implicit is better than explicit (under some condition), since 
> succinctness is power.

Almost all method calls in Ruby are not that implicit. I don't know why 
you'd make a special case out of to_a if you don't want to_a to be the 
default while not wanting to_ary to apply all of the time. But then I 
don't understand why to_a is not good enough for you because I don't 
understand what's too general about it and I don't know what's the 
difference between an array, an array, an array, and an array.

  _ _ __ ___ _____ ________ _____________ _____________________ ...
| Mathieu Bouchard - t駘:+1.514.383.3801 - http://artengine.ca/matju
| Freelance Digital Arts Engineer, Montr饌l QC Canada