using a module for these tasks actually *adds* complexity to your code

Well, yes and no. It adds complexity and also adds insurance against bitrot. The price paid turns out to be a win if there was an unforseen set of circumstances that could cause the technique to fail, e.g. funky stuff involving lazy loading or what have you.

With a module, the extra level of indirection gives you a chance to come up with a fix, safe in the knowledge that anything that uses it will inherit the improvement. Doing this in bare code means you have to go and hunt it down in the codebase if you ever need to fix it.

• another intruder with the mooring in the heart of the Perl

In reply to Re^5: Dynamically Changing Your Namespace by grinder
in thread Dynamically Changing Your Namespace by Ovid

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.