| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Subject: | Re: meson vs make: missing/inconsistent ENV |
| Date: | 2023-02-27 12:33:33 |
| Message-ID: | f5a573f0-f453-261a-99df-16b7b395a107@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-02-27 Mo 06:17, Dagfinn Ilmari Mannsåker wrote:
> Justin Pryzby<pryzby(at)telsasoft(dot)com> writes:
>
>> On Sun, Feb 26, 2023 at 03:21:04PM -0800, Andres Freund wrote:
>>>> Is there any consideration of promoting these or other warnings to
>>>> fatal?
>>> You mean the perl warnings?
>> Yes - it'd be nice if the warnings caused an obvious failure to allow
>> addressing the issue. I noticed the icu warning while looking at a bug
>> in 0da243fed, and updating to add ZSTD.
> Perl warnings can be made fatal with `use warnings FATAL =>
> <categories>;`, but one should be careful about which categories to
> fatalise, per<https://metacpan.org/pod/warnings#Fatal-Warnings>.
>
> Some categories are inherently unsafe to fatalise, as documented in
> <https://metacpan.org/pod/strictures#CATEGORY-SELECTIONS>.
>
Yeah.
It would be nice if there were some fuller explanation of the various
categories, but I don't know of one.
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2023-02-27 12:54:35 | Add error functions: erf() and erfc() |
| Previous Message | Dagfinn Ilmari Mannsåker | 2023-02-27 12:30:59 | Re: meson vs make: missing/inconsistent ENV |