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
Env::Export
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
several minutes ago. We don't need no stinkin' tactical nukes.
(By the way, do you have change for 10 million people?) --lwall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
I hope you're not serious (Score:1)
Hi Ovid
All you're doing is adding obfuscation to %ENV.
Big mistake.
Re: (Score:2)
Diagnosing $ENV{FEILD} is better? What's your solution?
Re: (Score:1)
Hash::Util's lock_keys seems like a good solution to me.
Re: (Score:2)
Except that sometimes people need to add environment variables. Boom!
Re:I hope you're not serious (Score:1)
Exactly right. At the very least, using PAR would be entirely out of the question. And you never know when someone down the road thinks *your* deployment strategy sucked big time and wants to do it over differently.
Reply to This
Parent