From: "Ara.T.Howard" Date: 2005-08-30T06:34:14+09:00 Subject: Re: Method behaves differently when called using #send On Tue, 30 Aug 2005, David A. Black wrote: > Hi -- > > On Tue, 30 Aug 2005, Daryl Richter wrote: > >> Yukihiro Matsumoto wrote: >>> Hi, >>> >>> In message "Re: Method behaves differently when called using #send" >>> on Mon, 29 Aug 2005 08:07:55 +0900, "David A. Black" >>> writes: >>> >>> |I don't think it's an overloading, just another (i.e., other than >>> |receiver-changing) nuance of the "more dangerous" concept. I actually >>> |didn't understand Matz's concern fully. I assume it's not >>> |specifically about the fact that send! is not destructive, since >>> |that's OK in a bang method. >>> >>> The point is not being destructive or not, since it's OK in a bang >>> method as you described (by quoting me). The point is that I don't >>> really feel it's dangerous to call private methods by the new method >>> (#fcall, or send!). They are just different. I'm hesitating put a >>> bang sign to something I don't feel dangerous. >>> >>> matz. >>> >> >> I'm a Smalltalker, so I agree that characterizing this as "dangerous" is >> overstated. I think "advanced feature" is perhaps more accurate? > > I'm a Rubyist, and I think it's a close call :-) Admittedly, part of my > clinging to send! is my desire not to see a completely different method name > for the non-private version. But I haven't come up with anything very > inspired by way of an alternative to fcall. dispatch(a_message, *args, &block) post(a_message, *args, &block) ?? -a -- =============================================================================== | email :: ara [dot] t [dot] howard [at] noaa [dot] gov | phone :: 303.497.6469 | Your life dwells amoung the causes of death | Like a lamp standing in a strong breeze. --Nagarjuna ===============================================================================