| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: use strict in all Perl programs |
| Date: | 2017-01-06 14:18:15 |
| Message-ID: | CAB7nPqTBwGNhc0guJtSS+rurj8UNaO6=Be+JCD2EvgJV+riS=w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 6, 2017 at 11:13 PM, David Steele <david(at)pgmasters(dot)net> wrote:
> With regard to warnings, I prefer to use:
>
> use warnings FATAL => qw(all);
>
> This transforms all warnings into errors rather than just printing a message
> to stderr, which is very easy to miss among the other output.
Interesting. A couple of warnings have slipped a couple of times in
some TAP tests like those of pg_rewind, so it could be useful to
switch to that at least for the tests by detault.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2017-01-06 14:18:33 | Re: Support for pg_receivexlog --format=plain|tar |
| Previous Message | David Steele | 2017-01-06 14:13:43 | Re: use strict in all Perl programs |