in reply to
Top Seven (Bad) Reasons Not To Use Modules
I am the choir that you are preaching to.
I find that the use of modules is the most compelling reason to use Perl. Once you get into the habit of looking on cpan before you code, you will find your productivity growing in leaps and bounds (as well as your reputation as a miracle worker at your job).
Let me share what happened to me this morning. I was writing code to deal with a really bad ticketing system that my company uses. The saving grace is that it is built on top of a database, so i can manipulate it's data.
I wrote a query that inserted formated data into a field in the db, but when i looked at the results in the app, the newlines were gone, replaced by black boxes. I (correctly) assumed that the app was expecting to see dos eol semantics, rather than unix.
I'm old and the part of my brain that remembers eol semantics punted them long ago to make room for something more important. But...
A quick search on cpan for "DOS NL" revealed the Text::FixEOL module, "cpan Text::FixEOL" installed it, and 2 lines of perl code implemented it. In less than 5 minutes, my problem was solved.
And because the modules is on cpan, i know it is tested on any platform i might ever use this code on, and i am far more sure that it is correct than I ever would be if I had implemented it myself.
"Worry is like a rocking chair. It gives you something to do, but it doesn't get you anywhere."