Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

I feel so inadequate (on CPAN) 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I also have three CPAN modules over the same timeframe, but that doesn't irk me in the least. Seeing people actually *use* my modules is what gets me all warm and fuzzy. I can't imagine supporting 10 or more active modules and maintaining my sanity. But for those who do, more power to ya! :)
  • I am kind of sceptical when it comes to people doing a lot of CPAN distributions. There's a pretty long way from an idea of a possible CPAN module to its implementation. For a reasonably complex module, this can take months with all the documentation and tests, interface-considerations etc. And that's only the first step. It has to be maintained afterwards

    Essentially I have a few unfinished modules lying around. My most ambitious project was probably porting the Aalib to Perl. I was mostly done with it (ev
    • My reply is remarkably old, so I apologize, but I feel I must clarify my original statements.

      Basically, I'm not spinning out CPAN modules for the hell of it; I can't tolerate "Hero Coding". On the other hand though, my modules were very small and, to me, seemingly inconsequential ones. Maintaining them has been very easy, mainly because there isn't much to go wrong.

      My original intention of this journal entry was to say that most of the code I've written could have been abstracted to a CPAN module, but w
      --
      -man Michael A Nachbaur
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.