The bug is not "accent in variable"
The bug is that in second eval the perl lexer can't parse normal variable anymore...Eval is useful to execute buggy code ... that's why i use it, because the code comes from user and he can always put "Unrecognized character"
And your are rigth , the way to solve the bug "accent in variable" is this way :
use Unicode::String;
my $code1='my $var_with_é_accent=5;print "var is $var_with_é_accent";'
+;
$code1="use utf8;$code1";
$code1=Unicode::String::latin1($code1)->utf8;
print "\nEval buggy code\n";
eval "$code1";
print "ERR = $@" if ($@);;
print "DONE\n";
my $string;
my $code2='$string="new eval done";';
print "\nEval good code\n";
eval $code2;
print "ERR = $@" if ($@);
print "string is : $string\n";
print "DONE\n";
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|