Re: perl checking - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: perl checking
Date
Msg-id 5ad08e4b-d9aa-3739-7b99-116d8e364a36@2ndquadrant.com
Whole thread Raw
In response to perl checking  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: perl checking  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List pgsql-hackers
On 5/18/18 14:02, Andrew Dunstan wrote:
> These two small patches allow us to run "perl -cw" cleanly on all our 
> perl code.

It's not clear to me what that really means.  My understanding is that
perl "warnings" are primarily a run-time instrument, unlike 'use strict'
and perl -c.  I have been playing with a private branch that adds 'use
warnings' next to 'use strict' across the perl scripts, and there are a
number of warnings that pop up at run time.  The fact that you get even
more warnings at compile time makes me wonder.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Postgres, fsync, and OSs (specifically linux)
Next
From: Justin Pryzby
Date:
Subject: Re: Should we add GUCs to allow partition pruning to be disabled?