From: James Britt <james_b@...>
Date: 2005-08-30T07:43:57+09:00
Subject: Re: Method behaves differently when called using #send

David A. Black wrote:
> Hi --
> 
> On Tue, 30 Aug 2005, Ara.T.Howard wrote:
> 
>...
>>
>>  dispatch(a_message, *args, &block)
>>
>>  post(a_message, *args, &block)
> 
> 
> My problem with this kind of name is that it isn't clear which one
> would include private methods and which one wouldn't.  It would be
> arbitrary, and one would just have to memorize it (and, in explaining
> it, would probably have to account for it as being "for historical
> reasons" or some such).
> 

Quite true, and, whatever name is picked, I hope it has a fairly 
intuitive (subjective, I know) relation to 'send', or a is plainly 
self-describing (also subjective, I know).

There are a few methods on Ruby whose names make sense if you have Unix 
or C experience.   There may be an argument for that sort of thing 
(though I'm unconvinced so far), but I'd prefer to see Ruby rely more on 
internal consistency than presumptions of some degree of geekery on the 
part of the user.


James

-- 

http://www.ruby-doc.org - The Ruby Documentation Site
http://www.rubyxml.com  - News, Articles, and Listings for Ruby & XML
http://www.rubystuff.com - The Ruby Store for Ruby Stuff
http://www.jamesbritt.com  - Playing with Better Toys