I can see your point here. Ive done things like this
sub assert{
my ($stmt,@args)=@_;
my $ok=eval"$stmt" or die "Failed to eval assertion '$stmt':$@";
unless ($ok) {
no warnings;
my $str=eval qq("$stmt")
or die "Failed to eval assertion '$stmt' as a string:$@";
die "Failed assertion '$str'\n";
}
}
which works reasonably well, but obviously isn't as satisfactory as your approach, and could even be a security risk as presently written if it were run on untrustworthy data.
Anyway, Itll be nice though when the new stuff is out at a production grade. I look forward to it. :-)
---
demerphq
<Elian> And I do take a kind of perverse pleasure in having an OO assembly language...
-
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.
|