First off, I love this module and would not enjoy writing large OO codebases in perl half so much without it.

I have nothing to add as far as naming goes, I like Aliased myself. *shrugs*

I hated the as at first, but then reading your reasoning I decided that I'm just stuck up and am used to The Way Things Are. Although I have to say that any self respecting OO module should not be using import()... but maybe I'm just not twisted enough yet.

For the actual useful bit of my post, have you considered dieing if the aliased name already exists in the target namespace? That would stop use Aliased 'My::Foo::Bar'; and use Aliased 'My::Bar::Bar'; from being able to trample one another and have there be no clue until the test suite breaks

In reply to Re: Module Naming Dilemma by Tuppence
in thread Module Naming Dilemma 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.