It needs to be packaged as a proper CPAN module. This requires a .tar.gz file, .zip won't do. I noticed that you have an install.perl and test1.perl program. The perl Makefile.PL; make; make test; make install sequence is required for acceptance. Proper module generation always starts with h2xs. Now you are facing the tedious work of starting a new module with h2xs and pasting your code into it. Running h2xs will help you fix the naming, directory, and Makefile problems.

One of the most critical areas of the documentation is the synopsis. It should be possible to cut and paste the entire synopsis and create a working program that shows the utility of the module. While the synopsis of Exporter::VA does compile, it doesn't stand alone as a useful program. The synopsis is the equivalent of a 'hello world' program in a new language and programming environment. Think of the module as a shrink-wrapped box, and the user wants to tear off the plastic and make it work as soon as possible. Perhaps the rest of the manual will be read later, after the initial frenzy is over.

The pod needs to include examples that actually work. Foo, bar, and baz have limited utility. I need to see an example in the pod of how your module improves the use of a real CPAN modules.

The $VERSION number is also unrealistic, given that the pod states that it has only been tested on AS/Windows. While perl code is remarkably portable, the idea that pure perl code will port with zero testing is unrealistic. A reasonable version number is perhaps 0.0121, not 1.21. Much of porting deals with installation and other issues that don't seem to have anything to do with the intended use of the code.

It should work perfectly the first time! - toma

In reply to Re: My module - my latest step by toma
in thread My module - my latest step by John M. Dlugosz

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.