in reply to Warnings and Strict in Production/Performance

This is scarier than Kim Jong Il:
Due to the way our system is architected, it likes to crap out if a script generates a warning, but it will do so silently. There's no way for us to know if a script dived out because of a warning or successfully sent its output to the next system.
Keep the warnings, fix the system. Add some logging to find your problem.

andyford
or non-Perl: Andy Ford

  • Comment on Re: Warnings and Strict in Production/Performance