Yes, backwards compatibility is a must. Nobody should have used any other module directly, nothing was documented that way (and the module source is almost devoid of any comment), so the chance is slim. Of course, there always might be that daredevil who knows better.

I did check the others on the same namespace (PDF::<xxx>) and there is a bunch, but nothing will collide. I thought to rename them anyway (PDF::Create::Page -> PDF::CreatePage, PDF::Image::GIF -> PDF::CreateGIF) to make it obvious that they belong together.

I'm worried too about side-effects of CPAN. For example, what will happen to the (now orphaned) subdirectories ?

Markus

In reply to Re^2: Simplifying CPAN module namespace by markus_b
in thread Simplifying CPAN module namespace by markus_b

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.