From: Christian Neukirchen Date: 2005-08-31T22:34:14+09:00 Subject: Re: Method behaves differently when called using #send "David A. Black" 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.) > My wanting abc and __abc__ to do the same comes from the fact that > that's how they've always worked. I don't want __ to suddenly mean > "name protection" in one place and "dangerous (like !)" somewhere > else. I see, and that is a valid opinion of course. I guess we better stop arguing now and let matz choose the names. Then we still can complain. :-) > David -- Christian Neukirchen http://chneukirchen.org