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.

Idle thought 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • The first company that I worked at used a lot of awk scripts and one-liners. We ended up moving to perl due to some limitations of awk (if I remember correctly it had to do with the max size of records that awk could handle).

    When I moved to my second company perl wasn't used at all which is very surprising considering the code base was in the millions of LOC and a good portion of that was reports/extracts/loads. I promoted perl heavily from day one and after solving some internal requests with perl very

    • Oh, I know how that came to be. I also firmly believe that Perl, even as Perl5, will continue to be successful as a workhorse because it lends itself so well to small tasks. Only Ruby comes close; Python is not going to steal mindshare among those who frequently write very short, disposable code. Once you’re catching small fish with a tool that’s capable of hunting bigger ones, you’re likely to use it lots.

      However, all of that really is tangential to the main point I was pondering, which

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.