From: dblack@...
Date: 2006-07-04T01:24:49+09:00
Subject: Re: About 1.9 #__method__ feature.

Hi --

On Tue, 4 Jul 2006, Mauricio Fernandez wrote:

> On Tue, Jul 04, 2006 at 01:00:30AM +0900, dblack@wobblini.net wrote:
>>> hmmm the link between "might be called externally despite being private"
>>> and "functional" is subtle, to say the least; #invoke_private_method seems
>>> much clearer (even if inaccurate) and is nearly as long if you want to
>>> discourage its use.
>>
>> I think it's inaccurate to the point of really not being usable.
>
> Conceded. #invoke_even_if_private also came to mind but it seems a bit
> excessive.
>
>> I admit I'm still a fan of send/send! but I guess they're long gone
>> :-)
>
> I also like it (! never really meant "danger" to me).

I like it too, and ! always *did* mean "danger" to me :-)  (And to
Matz, I always thought, but maybe I'm out of date.)  The "danger" in
this case is the inclusion of methods you normally wouldn't be able to
call and might not even know about.


David

-- 
  "To fully realize the potential of Rails, it's crucial that you take
    the time to fully understand Ruby--and with "Ruby for Rails" David
       has provided just what you need to help you achieve that goal."
       -- DAVID HEINEMEIER HANSSON, in the foreword to RUBY FOR RAILS.
  Complete foreword & sample chapters at http://www.manning.com/black!