The biggest problem with renaming your modules is, of course, the many references made to your module throughout your code. It's usually a fairly morbid experience to grep through thousands of lines of code and make sure all names are correctly changed. Global search and replace makes this easier, but the problem can be pre-empted in initial development.

my $pkg = "My::Package" ; eval "use $pkg ;" #you can also reference the package base class from a var my $obj = $pkg->new ;


Now you can easily change the package names just by changing the definition of $pkg.

I hope that helps.

Bro. Doug :wq

In reply to Re: Renaming CPAN modules by Bro. Doug
in thread Renaming CPAN modules by b10m

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.