On Fri, Jun 11, 2010 at 4:32 AM, Yukihiro Matsumoto <matz / ruby-lang.org> wrote:
> Hi,
>
> In message "Re: Why private #binding?"
>        >
> |> Probably you want something different from binding, maybe restricted
> |> eval environment, do you?
> |
> |Is it truly different? How does one get restricted eval environment
> |without binding?
>
> At least, you don't want some part of the current binding attributes.
> You are free to use binding to implement restricted eval environment,
> but if you want to change the binding behavior, it's different story.
> Right now, I don't feel making it public is worth changing, when you
> can define a small function to create binding for restricted
> environment.

Which is what I suggested. That's the beauty of Ruby, a programmer can
extend it without having to change it for the rest of us.

-- 
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