pgsql: Standardize order of use strict and use warnings in Perl code

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Standardize order of use strict and use warnings in Perl code
Date: 2020-09-21 15:06:30
Message-ID: E1kKNOg-0007PP-L9@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Standardize order of use strict and use warnings in Perl code

The standard order in PostgreSQL and other code is use strict first,
but some code was uselessly inconsistent about this.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/80fc96eceb817d89cdd11c02c8ab913c8d060a3e

Modified Files
--------------
doc/src/sgml/generate-errcodes-table.pl | 2 +-
src/backend/parser/check_keywords.pl | 2 +-
src/backend/storage/lmgr/generate-lwlocknames.pl | 2 +-
src/backend/utils/generate-errcodes.pl | 2 +-
src/pl/plpgsql/src/generate-plerrcodes.pl | 2 +-
src/pl/plpython/generate-spiexceptions.pl | 2 +-
src/pl/tcl/generate-pltclerrcodes.pl | 2 +-
7 files changed, 7 insertions(+), 7 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2020-09-21 16:44:42 pgsql: Copy editing: fix a bunch of misspellings and poor wording.
Previous Message Heikki Linnakangas 2020-09-21 11:57:48 pgsql: Fix checksum calculation in the new sorting GiST build.