in reply to Re^3: hex numbers
in thread hex numbers

The practice is inherently easy to make unsafe, though.

This is true. I should have posted the following rewrite of your example

# This works but is NOT recommended, and can be unsafe. my $s = "0xDEADBEEF"; # here we assign from a constant - but where # does the value come from in your code? my $n = eval $s; print "$n\n"; # Output: # 3735928559

which makes that point clear. It is not the eval of a string constant, hard coded into a program which is unsafe, but eval'ing a string from elsewhere.

perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'

Replies are listed 'Best First'.
Re^5: hex numbers
by davido (Cardinal) on Jan 14, 2021 at 20:17 UTC

    That is totally reasonable.

    My assumption was that if I didn't throw up a big red flag that implementation would have been the one that got used, and then we would be promoting a high risk behavior. Your comment is better.


    Dave