| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: warning handling in Perl scripts |
| Date: | 2012-06-25 16:07:55 |
| Message-ID: | 23709.1340640475@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"David E. Wheeler" <david(at)justatheory(dot)com> writes:
> Hrm, I think that `use warnings 'FATAL';` might only work for core warnings. Which is annoying. I missed what was warning up-thread, but the most foolproof way to make all warnings fatal is the originally suggested
> local $SIG{__WARN__} = sub { die shift };
Sigh, let's do it that way then.
> A *bit* cleaner is to use Carp::croak:
> use Carp;
> local $SIG{__WARN__} = \&croak;
Just as soon not add a new module dependency if we don't have to.
In this case, since we're not really expecting the warnings to get
thrown, it seems like there'd be little value added by doing so.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ryan Kelly | 2012-06-25 16:15:46 | Re: warning handling in Perl scripts |
| Previous Message | Robert Haas | 2012-06-25 16:06:25 | Re: pg_upgrade broken by xlog numbering |