postgresql/contrib/seg
Peter Eisentraut c538592959 Make all Perl warnings fatal
There are a lot of Perl scripts in the tree, mostly code generation
and TAP tests.  Occasionally, these scripts produce warnings.  These
are probably always mistakes on the developer side (true positives).
Typical examples are warnings from genbki.pl or related when you make
a mess in the catalog files during development, or warnings from tests
when they massage a config file that looks different on different
hosts, or mistakes during merges (e.g., duplicate subroutine
definitions), or just mistakes that weren't noticed because there is a
lot of output in a verbose build.

This changes all warnings into fatal errors, by replacing

    use warnings;

by

    use warnings FATAL => 'all';

in all Perl files.

Discussion: https://www.postgresql.org/message-id/flat/06f899fd-1826-05ab-42d6-adeb1fd5e200%40eisentraut.org
2023-12-29 18:20:00 +01:00
..
data
expected Replace last PushOverrideSearchPath() call with set_config_option(). 2023-05-08 06:14:07 -07:00
sql Replace last PushOverrideSearchPath() call with set_config_option(). 2023-05-08 06:14:07 -07:00
.gitignore Build all Flex files standalone 2022-09-04 12:09:01 +07:00
Makefile Remove distprep 2023-11-06 15:18:04 +01:00
meson.build Update copyright for 2023 2023-01-02 15:00:37 -05:00
seg--1.0--1.1.sql
seg--1.1--1.2.sql
seg--1.1.sql
seg--1.2--1.3.sql
seg--1.3--1.4.sql
seg-validate.pl Make all Perl warnings fatal 2023-12-29 18:20:00 +01:00
seg.c Convert contrib/seg's input function to report errors softly 2022-12-23 09:17:24 -05:00
seg.control
segdata.h Convert contrib/seg's input function to report errors softly 2022-12-23 09:17:24 -05:00
segparse.y Convert contrib/seg's input function to report errors softly 2022-12-23 09:17:24 -05:00
segscan.l Handle \v as a whitespace character in parsers 2023-07-06 08:16:24 +09:00
sort-segments.pl Make all Perl warnings fatal 2023-12-29 18:20:00 +01:00