Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked

Re: Bug : eval and accent

by erroneousBollock (Curate)
on Nov 16, 2007 at 09:55 UTC ( #651154=note: print w/replies, xml ) Need Help??

in reply to Bug : eval and accent
in thread Bug : eval and accent

Don't need eval.

use strict; use warnings; my $var_with__accent;
Gives the error:

Unrecognized character \xE9 at line 4.

WinXP SP2, ActivePerl 5.8.8 (build 817).

I guess you could argue that the error "breaks" the parser, and that it shouldn't really propagate outside of an eval.

Do the Perl docs actually say you can have non-ascii variable names?


Replies are listed 'Best First'.
Re^2: Bug : eval and accent
by Corion (Patriarch) on Nov 16, 2007 at 10:29 UTC

    All of this is on 5.8.3, ActiveState build 809

    Yes, the bug is that an error within eval should not affect other evals. I'm not sure where the problem lies, because the following code still works as expected and raises no error, no matter whether $string is a global or a lexical variable:

    use strict; use Test::More tests => 12; sub second_eval_unaffected($) { my ($code) = @_; eval $code; diag $@ if $@; my $string = ''; ok eval(q($string="new eval done";)), "Eval after >>$code<< still +works"; is $@, '', "... and raises no error either."; is $string, 'new eval done', "... and sets the variable correctly" +; }; second_eval_unaffected 'my $var_without_accent;'; second_eval_unaffected 'my $var_with = "_accent";'; second_eval_unaffected 'my statement_with_error;'; second_eval_unaffected 'my $var_with__accent";';

    This program exhibits the problem as a self-contained Test::More program. The first sequence of steps leads to a failure, while the second run succeeds. This should not happen, but I don't know why :)

    use strict; use Test::More tests => 10; sub gauntlet { my $code1=shift; my $string; my $expected = "new eval done"; my $code2='$string="new eval done";'; ok eval($code2), "Good code evals correctly"; is $@, '', "... and raises no error on its own."; diag "Eval trial code\n"; diag $code1; eval $code1; diag '$@ is ', $@; undef $string; diag "Eval good code ($code2)\n"; ok eval $code2; is $@, '', "No error raised"; is $string, $expected; }; gauntlet('my $var_with__accent;'); gauntlet('my $var_without_accent;');
Re^2: Bug : eval and accent
by ikegami (Patriarch) on Nov 16, 2007 at 10:17 UTC
    The error is properly caught by the first eval. That's not the problem. The problem is that the error causes subsequent evals to work incorrectly (silently unable to access lexicals, at least).
Re^2: Bug : eval and accent
by sylvanus_monachus (Novice) on Nov 16, 2007 at 10:09 UTC

    i have made a new post with renders element...

    in fact we eval code feeded by user ... i know that variables are ascii in perl but my users don't ... and ours application need to do more eval after evaluating buggy code of user...

      Evaling user code is dangerous. If you can use a hash instead, you bypass the naming problem.

Log In?

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://651154]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (3)
As of 2022-05-27 22:03 GMT
Find Nodes?
    Voting Booth?
    Do you prefer to work remotely?

    Results (98 votes). Check out past polls.