I'm not convinced I like any of the above when it comes to readability. Here is what I came up with that might make it easier for a junior-level programmer to at least have half a clue as to what is going on (it being understood that my choice of variable names could be better):
sub id2path_boftx
{
my $id = shift or return q();
# my $chunk_length = length $id > 6 ? 3 : 2;
my $chunk_length = $id < 1e6 ? 2 : 3;
my $path_pat = '%0' . $chunk_length . 'd';
$path_pat = join('/', $path_pat, $path_pat, $path_pat);
my $chunk_power = 10 ** $chunk_length;
my $path = sprintf $path_pat, $id / ($chunk_power ** 2),
($id / $chunk_power) % $chunk_power, $id % $chunk_power;
return $path;
}
FWIW, it passes all 23 tests.
Update: Changed how $chunk_lentgh is determined. I like the numeric test better after looking at it for a while.
It helps to remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.