Hi T.

 > The way I see it, eval's not just about running code in different
 > bindings and class/instance modes, but also pulling information to do
 > it with from surrounding scope. That's why I suggested the concept of
 > scope "holes", which forgoes the need to turn an object into a string
 > literial in order to be eval'd, which can be very burdensome if you
 > have a complex object.

Haven't you seen my proposal in [ruby-talk:86349] using define_method? 
Or didn't it work for you?

Regards,
Pit