Flags aren't always a bad thing.
while ( ... ) {
if (!$flag && check_whatever()) {
do_whatever();
$flag = 1;
}
}
I'd suspect that the best way of putting this into the core would be simply by setting/checking a flag at the C (or Parrot, I guess) level instead of the Perl level. I suppose that, after a single execution you could actually remove the relevant ops from the tree altogether, but I'd have to wonder at the efficiency of that in all but very long running loops.
Making it a language feature in Perl 6 might make some sense as it would allow the programmer to avoid the use of flag. I don't see the point in jumping through any hoops to implement this in Perl 5 though.
-sauoq
"My two cents aren't worth a dime.";
-
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.
|