Re: What about Perl autodie?

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, John Naylor <johncnaylorls(at)gmail(dot)com>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>
Subject: Re: What about Perl autodie?
Date: 2024-03-19 06:29:18
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 18.03.24 09:17, Daniel Gustafsson wrote:
>> On 18 Mar 2024, at 07:27, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>> After some pondering, I figured the exclude list is better.
> Agreed.
>> So here is a squashed patch, also with a complete commit message.
> Looks good from a read-through. It would have been nice to standardize on
> using one of "|| die" and "or die" consistently but that's clearly not for this
> body of work.


I was aware of the semantic difference between "||" and "or", and I had
tried to keep it similar to surrounding code.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Li, Yong 2024-03-19 06:48:33 Re: Proposal to add page headers to SLRU pages
Previous Message Aadhav Vignesh 2024-03-19 06:23:19 Proposal: Introduce row-level security templates