Good, thanks for explaining yourself. My apologies for the knee-jerk reaction, I should have noticed our mutual communication error earlier and pointed it out, but it was a little hard to grok. We are at least 90% on the same page, which for all practical purposes is good enough.
But, to create an aggregate class simply to collect things ... that's the red flag.
Then this is why we've had all of this confusion. I had no idea you were pointing out what you considered a red-flag in Limbic's code, rather than mine (I was using map). Thanks for clearing this up. To be fair to Limbic, there are analogous situations where this might make sense, for instance if he was implementing some sort of spiffy event notification list or message dispatch table, in some form or another -- but it would need some tweaking to be that versus what I see in it now.
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.