Re: New module name? Pod::Pdf2

John Bokma wrote:

"Lee" <leegee@xxxxxxxxx> wrote:

... I have an almost-publishable module to turn POD into PDF. Pod::Pdf is
rather old, doesn't handle multiple files nicely[1], and is very hard
to extend since it uses neither Pod::Parser nor PDF::API2.

Thinking of calling the module Pod::Pdf2.

[1] I have submitted an updated version to the Pod::Pdf author, to both
publish his =inclue POD extnesion for including multiple files, and to
allow a POD PDF of a (recursed) directory, but wrote the new module in
the week sine.

How about trying to contact the author and see if he's willing to let you
maintain Pod::Pdf? That way you can put your new module into action
without adding another module to CPAN. Especially if it's possible to
support all old methods.

Personally I think that cluttering CPAN with almost similar modules is a
bad idea, even if they are better.

I quite agree about cluttering with near-identical modules.

I'm not sure I'd call my module 'better' - rather it is clearer to the
average non-PDF-reader (like myself) since it does not write direct PDF
like Pod::Pdf, but uses the excellent perl interface (PDF::API2). It
also sub-classes Pod::Parser, which makes extension quite easy.

Doesn't that count as additionaly functionality...?

I'd not want to overwrite the existing module, though, it produces such
beautiful output....

.