Hi --

On Mon, 29 Aug 2005, Douglas Livingstone wrote:

> On 8/29/05, Jeff Wood <jeff.darklight / gmail.com> wrote:
>> It breaks encapsulation for anything to call a private method other than
>> the object itself... So, I guess it needs to have scope...
>>
>
> We have open classes remember :)
>
> It isn't so much a problem that send/send! can break encapsulation,
> rather it is "when you want to break encapsulation, how do you want to
> do it?"

And I think Matz's goal in this is to "purify" send, isolating the
privacy-invading behavior in a different method.


David

-- 
David A. Black
dblack / wobblini.net