From: Rick DeNatale <rick.denatale@...>
Date: 2010-06-11T02:09:59+09:00
Subject: Re: Why private #binding?

On Thu, Jun 10, 2010 at 1:01 PM, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
> Hi,
>
> In message "Re: Why private #binding?"
>    on Thu, 10 Jun 2010 22:29:32 +0900, Rick DeNatale <rick.denatale@gmail.com> writes:
>
> |I can think of two potential reasons.
> |
> |1. Because binding exposes the internals of the receiver.
> |
> |2. because if it were public then in a case like:
> |
> |
> |class A
> |    def self.binding_of(b)
> |        b.binding
> |    end
> |end
> |
> |A.binding_of("abc")
> |
> |might well return a binding with self == A, rather than the string,
> |because binding returns the bindings "at the point of call"
>
> The latter one was the biggest reason for me.

Knowing you, I suspected that that was the case.   It would be for me as well.

-- 
Rick DeNatale

Blog: http://talklikeaduck.denhaven2.com/
Github: http://github.com/rubyredrick
Twitter: @RickDeNatale
WWR: http://www.workingwithrails.com/person/9021-rick-denatale
LinkedIn: http://www.linkedin.com/in/rickdenatale