comment on

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":

Are you posting in the right place? Check out Where do I post X? to know for sure.

Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).

Want more info? How to link or How to display code and escape characters are good places to start.


Syntactic Confectionery Delight
	PerlMonks