I have some perl code that literally tens of people might be interested in. Although I've used perl for a decade, it has been a long time since I've coded anything other than simple ad-hoc scripts in it. So I'm pretty new to the OO perl model (I've written a book on Java, but perl OO is a little more, well, exotic!)

Anyways, the module is designed to allow you to read data from a closed, old 4GL called "FilePro."

I built the module following the guidance in the Apress title "Writing Perl Modules for CPAN." Even with that, I've already seen things I know I should change. I'll switch from "die" to "croak" and so on.

Basically, I'm hoping someone will take a look and make recommendations for things I should address prior to offering it up on CPAN. I've got my PAUSE account and such, but I'd like someone besides me to look at it.

You can get to the code at my website (and take it easy, this server runs in my home!)

http://www.technodane.com/code/FilePro-Data-0.01.tar.gz

Like I said, I'm new to the formal module game. I'm seeking advice on writing tests, on documentation best practices, namespace (filePro appears to be a registered trademark; tips on that?)

An implementation detail: My iterator model uses a hash key string as a "handle." It would probably be better to use another "object" for that, but I'm not clear on the best way to do that. Does it make sense to put more than one "package" in a single CPAN module? Should the iterator be separate module on which FilePro::Data depends?

Any tips would be welcome!

In reply to Proposed module for CPAN for FilePro data file reading by tdane

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.