I'm having difficulty understanding what you are saying since it says "Is
there a reason we're switching from #*send* to #send?". I assume you are
saying why change from #__send__ to #send. I found there was inconsistency
in the use of the two so I switched all to send. I also find __send__ to be
annoying to read. I use to use __send__ everywhere when I was first coding
ruby because I was surprised that a base function was named send, and I
think most of these cases of __send__ came from me. Is there really risk of
#send overrides in these situations?


On Fri, Jan 17, 2014 at 3:15 PM, Tony Spataro <notifications@github.com>wrote:

> In lib/right_agent/dispatcher.rb:
>
> >        else
> > -        actor.__send__(method, request.payload, request)
> > +        actor.send(method, request.payload, request)
>
> Is there a reason we're switching from #*send* to #send?
>
> I doubt that #send is overridden on any class where we're calling it, but
> the rubyist best practice is to call *send* if your intent is to dispatch
> a method to the object (in case that object overrides #send to do some
> app-level operation).
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/rightscale/right_agent/pull/99/files#r8983641>
> .
>