On Wed, 14 Jan 2009 10:51:35 +0900, Charles Oliver Nutter wrote:

> Yukihiro Matsumoto wrote:
>> One possible idea is making "binding" read-only, or noting that eval
>> with binding may not modify the original binding.
> 
> That would be a reasonable compromise. So binding would make a copy of
> the captured scope, rather than reference it. It seems like there are
> few use cases for being able to capture a binding and mutate captured
> values.
> 
> - Charlie

A use case for mutable bindings with Proc#binding was presented in the 
Reference class in http://onestepback.org/index.cgi/Tech/Ruby/
RubyBindings.rdoc/style/print and ruby-talk:321138

At least from a theoretical standpoint, it's pretty compelling.

--Ken


-- 
Chanoch (Ken) Bloom. PhD candidate. Linguistic Cognition Laboratory.
Department of Computer Science. Illinois Institute of Technology.
http://www.iit.edu/~kbloom1/