You should see the recursive version for processing arbitrarially deep nested hashes :)
On a serious note. I find short to be good for mainatainence. It may require me to look longer before I start making changes, but I consider that a good thing.
Too many times I've been bitten by zeroing in on what looked to be (or the comments indicated as), a self contained piece of code, only to find out later that there was another piece just off screen that was affected.
It's a personal thing, but if I don't understand a piece of code froom reading it, then I prefer to experiment (in a test program or with the debugger) until I do, rather than be swayed into believing that I understand it by reading another programmer's, or even my own, comments.
Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon
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>
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
Want more info? How to link
or How to display code and escape characters
are good places to start.