Hi --

On Wed, 31 Aug 2005, Christian Neukirchen wrote:

> "David A. Black" <dblack / wobblini.net> writes:
>
>>> It is interesting you want #abc and #__abc__ to do the same, but don't
>>> care if #send sends a mail and #send! a message...
>>
>> I'm not sure what you mean.  (Mail?)  My suggestion was that send!
>> would be the "dangerous" version of send.  They'd both send messages
>> to objects.  Again, it's moot, but the whole thing was fully contained
>> within what send does now -- just sharing it between two methods.
>
> The problem is that lots of classes redefine #send, just because the
> same is so convenient.  When they redefine #send, #send and #send!
> mean something completely different, and that is confusing.  (More
> confusing to me than having #__send__ and #send do something
> different.)

Oh, I see what you mean.  I guess it would be __send__ and __send__!
:-)


David

-- 
David A. Black
dblack / wobblini.net