Another issue I can see with this approach is that it's
not terribly obvious. Not that one should write nothing but
pedestrian code -- if this is the right thing to do, then do
it -- but I can easily imagine some poor maintenance
programmer looking at this code and thinking "WTF? Why
didn't he just use a HoH?"
Another point: specific operations will be O(1) instead
of O(depth) if you know exactly where you want to go (i.e.
you have a hash key already), but building the key may be
O(depth), depending on how much information you have ahead of
time. (And if speed's your concern, you can always
reference the first time you need it.)
In general, I'm not sure that this technique gives you
much of a win, but I'm not clever enough to prove that it'll
never be useful. :-) Nice job, and thanks for making me
Found a typo in this node? /msg me
The hell with paco, vote for Erudil!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||