To be honest, I'm not facing a bunch of situations where I particularly want to avoid strict, warnings, etc. Or, rather, I want them to be worked out before production because if they happen in production and they're masked, I may never know that my data got silently munged.
As for the logging, warn-fatal, etc., I probably want most of those either in a logfile or in my commandlines (or both).
I standardised our logging tools and exception handling mechanisms by centralising them in a Log module. Admittedly, it isn't a great mechanism, but it does suffice for our purpose. And it's the same code for all our scripts. I also standardised a lot of other things by putting them in modules. Such as commandline handling.
I'm not saying your idea isn't good. I'm saying that if it is, I'm currently missing it.
In reply to Re: RFC: pragma 'use dev;'
by Tanktalus
in thread RFC: pragma 'use dev;'
by rvosa
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |