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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I recently wrote a post at perlmonks advocating why you should always install your own perl [perlmonks.org] and how you may run into issues with a vendor perl with a complex perl application.

    You've been able to shed a bit more light on why it's necessary, thanks for taking the time to write this out so eloquently.

    • Thank you. I'm glad to hear that my ideas were helpful, and even more glad just to hear someone say, "I agree," so I know I'm not crazy. :) Also, I appreciate your comment in your perlmonks post that your deployment should be testable, repeatable, and automatable. That's a large part of what I'm going for here.

      I'm about to post a short followup journal entry to this one that may interest you, too.

      --
      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers