I'd never thought it through particularly, since in my case it is much less likely anyone else will have to read my code, but readability does seem to be quite a personal thing. I think there are some styles that are going to be less readable for almost everyone, but a lot of cases where it's totally dependent on the reader. I probably betray my own sloppy habits when I say I found your version one easier to understand than version two.
My {pre-decimalisation pound} / 120 is that the map version wd be more readable like this:
my @files = map {&makefiles} @in;
sub
makefiles
{
my ($count, $file) = split;
$file =~ s/^$in_prefix//;
my ($campaign, $month, $fname) = split /\//, $file;
return { # not strictly necessary, but *readable*
campaign => $campaign,
month => $month,
file => $fname,
count => $count,
sort => "$campaign:$month:$file"
};
}
§ George Sherston
-
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.
|