Bart Lateur:
> If your P5->P6 translator is slow, i.e. written
> in Perl, this would imply a pretty big performace hit.
It is better for translated programs to do the right thing slowly than
to do the wrong thing as quickly as possible.
> What would help is a debugging mode that prints out the
On Fri, 15 Sep 2000 12:01:55 -0400, Mark-Jason Dominus wrote:
>When you translate a script, the translator should translate things so
>that they have the same meanings as they did before. If it doesn't
>also translate eval, then your Perl 5 scripts will be using the Perl 6
>eval, which isn't wha
> eval should stay eval.
Yes, and this is the way to do that.
When you translate a script, the translator should translate things so
that they have the same meanings as they did before. If it doesn't
also translate eval, then your Perl 5 scripts will be using the Perl 6
eval, which isn't wha
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
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
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
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
