(4) Thanks for criticizing my bad coding style (using map in a void context). I am digging into the link to find out why I should avoid to use this style... :)

Don't be too hard on yourself for this one. Void map/grep have been argued over for years in the perl community. Some don't see a problem with it, others do. Definitely look into the issue and decide for yourself what is right.

I'm personally neutral on void map. I use foreach in most cases where a void map could be used, because I think it more clearly expresses the intent of the code. However, I would have no problem using a void map if I thought it made things more readable.

You might like to check out this nice article on void map


TGI says moo

In reply to Re^3: how to store an array to a pseudohash? by TGI
in thread how to store an array to a pseudohash? by Hanken

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.