In this case, I'm not particularly inclined to complain
about the goto, though I find an explicit loop
a bit easier to read (in that the branching structure's
fairly well-defined; when I see a label, I look through all
the applicable code for gotos, even if I'm
fairly sure that there won't be more than the obvious one).
In my experience, the "goto EVIL!" meme is
propagated either by well-meaning but naive instructors who
don't want to "confuse" beginning programmers with the
vagaries of when gotos are appropriate, but
don't want their students picking up bad habits, or by
cargo-cult instructors who were taught that
goto is uniformly bad, didn't bother to
question the statement, and go on to teach others. Either
way, it's irritating, but probably a net win.
--
The hell with paco, vote for Erudil!
:wq
-
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.
|
