> -----Original Message-----
> From: william.w...@gmail.com [mailto:william.w...@gmail.com] On Behalf
> Of Bill Ward
> Sent: Wednesday, June 17, 2009 12:39 AM
> To: module-authors@perl.org
> Subject: lexical warnings question
>
> warnings. So, we want to make warnings fatal in the development
> environment to force developers to fix those niggling "uninitialized
At least be sure to limit that to " uninitialized " ones. I don't think making
every warning fatal is a good idea. Sometimes you may (at least I do) want to
report recoverable errors as a warning.
> So, do I need to monkey with $SIG{__DIE__} or something? I haven't
You'll need to set $SIG{__WARN__} for that. However, anyone can say local
$SIG{__WARN__} to bypass it. If you don't have any internal document that
decribes coding standards in your $job, I suggest defining it first and
implementing a code review process (if there isn't any) to improve code
quality. Well, the quality of the code may not change but you'll have something
standardized instead of random codes.
