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.

What are the "must have" modules? 1 Comment More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • Of course it depends to some extent on whatever I'm doing at the moment. However in addition to what's on your list I'd probably feel a little lost without:

    • Large chunks of Test::*
    • Kwiki - having a wiki per-project is my default behaviour now
    • CPAN::Mini - becoming my default way of managing modules for clients
    • DateTime - because it rocks
    • File::Find::Rule - because it also rocks
    • Devel::Size - for figuring out where all that memory went
    • HTTP::Recorder - web site testing and scraping
    • Module::Build - because I hate makefiles
    • Apache::Test - for testing... well you can probably guess
    • Cache - slow, but useful
    • Data::UUID - keep finding uses for it in the oddest places
    • CPANPLUS - because it has an API I can get at
    • Devel::Cover - because coverage reports give me the warm fuzzies
    • Devel::Profiler - it took how long?!
    • Exception::Class - saves typing
    • Hook::LexWrap - great for wedging stuff in
    • Mac::Growl - because growl rocks
    • Module::CoreList - to figure out what started working when
    • Template - coz I like it
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.