aboutsummaryrefslogtreecommitdiff
path: root/src/tutorial/basics.source
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2023-12-29 18:01:53 +0100
committerPeter Eisentraut <peter@eisentraut.org>2023-12-29 18:20:00 +0100
commitc5385929593dd8499cfb5d85ac322e8ee1819fd4 (patch)
treedf87a0618dea5cb1d41f0cd9e1faad27320c0438 /src/tutorial/basics.source
parent7418767f11d11ca4003ed3e8e96296eabb2acfe1 (diff)
downloadpostgresql-c5385929593dd8499cfb5d85ac322e8ee1819fd4.tar.gz
postgresql-c5385929593dd8499cfb5d85ac322e8ee1819fd4.zip
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
Diffstat (limited to 'src/tutorial/basics.source')
0 files changed, 0 insertions, 0 deletions