From: "Hal E. Fulton" Date: 2002-07-17T02:47:08+09:00 Subject: Re: TkText no -textvariable workaround? ----- Original Message ----- From: "Dossy" To: "ruby-talk ML" Sent: Tuesday, July 16, 2002 12:40 PM Subject: Re: TkText no -textvariable workaround? > On 2002.07.17, Hal E. Fulton wrote: > > > > > Dossy writes: > > > > > > > Speaking academically, the receiver is object a, the method is =(x). > [...] > > But seriously, I think Dossy is mistaken... except in the > > special case of attribute writers and accessors, assignment > > is never considered to be a method call in Ruby. Correct? > > I did say "academically" -- in a pure OO language where everything > is an object, the receiver would be the object a, and the method -- or, > the message being sent, would have been "=(x)" ... Yes, you're absolutely right in that sense. > I wonder how Ruby would have been different if Object#=(x) were defined > as an alias to #replace ... Actually, I've wondered the same thing. Sometimes I think this would be good. Sometimes it seems bad. Usually I just don't know. :) In a "radically object-oriented" language like Ruby, it seems natural that assignment *would* be a method (as it is even in C++ and Java). This leads me to think there must be a good reason why it is *not* implemented this way. Matz? :) Cheers, Hal Fulton