From: Robert Dober Date: 2007-01-24T05:49:13+09:00 Subject: Re: Minor Change Proposal for Classes 'Object' and 'Method' ------=_Part_231834_13772257.1169585350966 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 1/23/07, dblack@wobblini.net wrote: > > Hi -- > > On Wed, 24 Jan 2007, ara.t.howard@noaa.gov wrote: > > > very good points. frankly, i find the 'potentiality' arguments silly > since > > they're analogous to saying the we shouldn't use 'self' here > > > > class C > > def m() self end > > end > > > > since, at the time of writing the function, no 'self' yet exists. to be > > accurte we should probably use > > > > class C > > def m() furture_self end > > end > > > > but, of course, we don't. > > I've come to think that: > > m = a.method(:x) > m.call > > does not involve a receiving the message "x", in any useful sense of > the term "receiving". So I don't think it's just a matter of avoiding > "future" in a case where something will happen in the future; rather, > it's a different scenario from a.x. Sorry Ara I promised to bail out but I am just asking a question, just too curious. David I am losing you here, probably you just look further than me but as well on a conceptional view as on an implementation's view (method_call in eval.c if I recall correctly) m.call just sends the message :x to the object it is bound to. If you avoid that notion, what else could there be? Method invocation without message passing would this have benefits on the conceptional level? Hmm yes indeed it might close the discussion about receiver but I feel it would open a difficulty in describing this kind of invocation. Maybe it would be worth it. Far above my horizon but eager to learn. It's avoiding "receiver" in a > case where the object in question is not the receiver of the message > in question. > > But I'm in a tiny minority on every phase and nuance of this, so > that's probably that :-) Yes indeed if you prefer to answer offlist I would be very happy too. OTOH someone who has gone through the trouble and effort of going through a paradigm change will always be a minority first, right (c.f. my signature) David > > -- > Q. What is THE Ruby book for Rails developers? > A. RUBY FOR RAILS by David A. Black (http://www.manning.com/black) > (See what readers are saying! http://www.rubypal.com/r4rrevs.pdf) > Q. Where can I get Ruby/Rails on-site training, consulting, coaching? > A. Ruby Power and Light, LLC (http://www.rubypal.com) > > Cheers Robert -- "The best way to predict the future is to invent it." - Alan Kay ------=_Part_231834_13772257.1169585350966--