From: Trans Date: 2007-08-03T03:50:25+09:00 Subject: Re: #send in 1.9 On Aug 2, 12:32 pm, dbl...@rubypal.com wrote: > Hi -- > > On Fri, 3 Aug 2007, James Edward Gray II wrote: > > > On Aug 2, 2007, at 10:54 AM, Trans wrote: > > >> There doesn't seem any good reason to > >> change how #send works if we are just going to have the same > >> functionality in another ordinary method, ie. #funcall. > > > Well, there's the reason of the name of the method. You "send" an object a > > message and you shouldn't be allowed to send private messages. > > You're allowed to send any message; it's up to the object what to do > with it :-) You could similarly say that you can only call > non-private functions. > > In fact, the problem for me is that the names don't tell you what's > happening; you just have to know. I agree. A rose smells just as sweet . . . I just hate the thought of all the programs that will break for what seems like a rather minor distinction in semantics. T.