I suspect that pg meant to say "should not be exposed BY the class that holds the collection." Then it makes perfect sense.

This was a very nice reminder for me, anyway, of the usefulness of OOP in certain cases. Although I enjoy the freedom, speed, and flexibility of Perl, it doesn't mean that we should not use a little more structure when it's beneficial to do so.

I must admit that OOP is a weakness of mine, but I am diligently working to improve in that area.

pg's meditation was timely for me. Your question helped expose the crux of pg's point. That's why I'm voting for both of your nodes.

In reply to Re: Re: multi-tier collections & lack of modulization/OO by ccarden
in thread multi-tier collections & lack of modulization/OO by pg

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.