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
--Larry Wall in <199911192358.PAA24109@kiev.wall.org>
Did I say I expect Perl to do the right thing? :-)
--Larry Wall in <199911200217.SAA24898@kiev.wall.org>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
My point exactly (Score:1)
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.
Re:My point exactly (Score:2)
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
Reply to This
Parent