I find the first one clearer and easier to understand.
Our coding standards do not mandate "single point of exit";
by all means use it where it makes the code clearer, but enforcing it leads to clumsy, deeply nested code, with extra "flag" variables to keep state.
At least that's what I've seen.
In any case, with the growing use of exceptions in modern languages, single point of exit is somewhat illusory.
More important than single point of exit is to keep functions cohesive and short, with few parameters, and free of globals.
-
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.
|
