Well, if you use next to leave an eval, you're effectively leaving the eval container to get back to your main program or whatever. Logically, a next command should take you to a block in the same container, shouldn't it? I mean, if you write a subroutine with a next command, Perl would expect the next command to refer to a local label. Same with eval commands, I'm guessing. It's like pointing to someone in the Marketing department to get an Engineering task done, which defeats the purpose of encapsulating things into evals and subs. The 'damage' would be limited to confusion when/if things don't work as expected.
Update: hofmator below gives a better answer, I think. It basically comes down to the fact that eval isn't built specifically for looping, so you should probably use another structure (like do) if possible.
andre germain
"Wherever you go, there you are."
-
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.
|