From: Dossy Date: 2002-07-17T21:49:01+09:00 Subject: Re: TkText no -textvariable workaround? On 2002.07.17, Nat Pryce wrote: > From: "Dossy" > > 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)" ... > > > > I wonder how Ruby would have been different if Object#=(x) were defined > > as an alias to #replace ... > > I only know of one OO language, Self, where assignments are actually > implemented as message sends. In Self, there are only objects and messages. > Even stack frames are objects that you send messages to. Right. (IIRC, I believe Smalltalk also implements assignments as message sends and everything is an object or a message as well.) > To translate into Ruby terms, the statement "a = x" is conceptually sending > the message "a= (x)" to the local stack frame, rather than sending the > message "=(x)" to a. Right. Thanks for correcting me! -- Dossy -- Dossy Shiobara mail: dossy@panoptic.com Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70)