Re: 'eval' odd thought

[Bart Lateur]

On Thu, 14 Sep 2000 18:14:49 -0400, Mark-Jason Dominus wrote:

The perl 5 - perl 6 translator should replace calls to 'eval' with
calls to 'perl5_eval', which will recursively call the 5-6 translator
to translate the eval'ed string into perl 6, and will then eval the
result.

Blech, no. eval should stay eval. People are responsible for generating
Perl6 compatible code, if they construct code as strings on the fly.

Warning people when converting a script from perl5 to perl6, that a eval
STRING has been found, is a good idea.

-- 
Bart.

Re: 'eval' odd thought

[Dave Storrs]

On Fri, 15 Sep 2000, Bart Lateur wrote:

 On Thu, 14 Sep 2000 18:14:49 -0400, Mark-Jason Dominus wrote:
 
 The perl 5 - perl 6 translator should [recursively handle eval]
 
 Blech, no. eval should stay eval. People are responsible for generating
 Perl6 compatible code, if they construct code as strings on the fly.

I would disagree.  If I'm using a program to translate my code
from one version of Perl to another, I don't want to have to go in and
hand-fix (possibly large) sections of it...it should just _work_.  I'm
with MJD on this one.

Dave

'eval' odd thought

[Mark-Jason Dominus]

The perl 5 - perl 6 translator should replace calls to 'eval' with
calls to 'perl5_eval', which will recursively call the 5-6 translator
to translate the eval'ed string into perl 6, and will then eval the
result.

Mark-Jason Dominus   [EMAIL PROTECTED]
I am boycotting Amazon. See http://www.plover.com/~mjd/amazon.html for details.

Re: 'eval' odd thought

[David L. Nicol]

Mark-Jason Dominus wrote:
 
 The perl 5 - perl 6 translator should replace calls to 'eval' with
 calls to 'perl5_eval', which will recursively call the 5-6 translator
 to translate the eval'ed string into perl 6, and will then eval the
 result.

And that gives us a convenient name space for inlining other more or
less alien languages

ML_evalEND_ML_SECTION;