On Jun 11, 2004, at 8:08 AM, gabriele renzi wrote:

> il 11 Jun 2004 07:59:05 -0700, llothar / web.de (Lothar Scholz) ha
> scritto::
>
>> Nicholas Van Weerdenburg <nick / activehitconsulting.com> wrote in 
>> message news:<40C92E6E.9040708 / activehitconsulting.com>...
>>> A compiler could attempt to translate evals into other constructs. I
>>> think most are simple enought to do that.
>>
>> No. Simply grep through the 1.8.1 standard library and you  see that
>> it is used a lot in non trivial situations.
>
> yet, there are places where it may be avoided, say, in tkfont.rb:
>  obj.instance_eval{ initialize(src) }
> maybe could become:
>  obj.send(:initialize,src)
>
> There should be interest in this kind of changes, apart from
> compilation problems?

Would instance_evals (assuming they take blocks) really be that big of 
a problem? The way I see it, as long as it just takes a code block, 
that part is compilable; all it takes is a change of the 'self'. But if 
it takes a String, that must be compiled into code at runtime, and...

cheers,
Mark