From: "David A. Black" <dblack@...>
Date: 2009-07-15T20:55:49+09:00
Subject: Re: Twelve rules of Ruby

--1926193751-1490150871-1247658935=:11289
Content-Type: MULTIPART/MIXED; BOUNDARY="1926193751-1490150871-1247658935=:11289"

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--1926193751-1490150871-1247658935=:11289
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8BIT

Hi --

On Wed, 15 Jul 2009, lith wrote:

>> 2. Objects don't "have" methods; they have the intelligence to resolve
>> � � messages by looking for methods along their class/module lookup
>> � � path.
>
> Since methods are bound to a certain evaluation context (ie the object
> aka self), isn't that statement slightly simplicistic in that it
> suggests a unidirectional relationship? The word "have" would IMHO
> better reflect the reciprocal dependency. But English isn't my mother
> tongue and maybe I got certain details wrong.

As I've said in other posts in this thread, the point isn't really to
get people to stop saying "have", but rather to get them to *start*
understanding how the Ruby object model works. Saying "have" is what
we all gravitate toward -- which is fine, except it doesn't pay you
back when you examine it closely trying to figure out what's really
going on.

Thus the troubleshooting of the "have" model is specifically a way of
getting relative newcomers to Ruby to think more carefully about the
object model.


David

-- 
David A. Black / Ruby Power and Light, LLC
Ruby/Rails consulting & training: http://www.rubypal.com
Now available: The Well-Grounded Rubyist (http://manning.com/black2)
Training! Intro to Ruby, with Black & Kastner, September 14-17
(More info: http://rubyurl.com/vmzN)
--1926193751-1490150871-1247658935=:11289--
--1926193751-1490150871-1247658935=:11289--