public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: Bertrand Drouvot <[email protected]>
Cc: Álvaro Herrera <[email protected]>
Cc: Michael Paquier <[email protected]>
Cc: Heikki Linnakangas <[email protected]>
Cc: Quan Zongliang <[email protected]>
Cc: [email protected]
Subject: Re: Consistently use the XLogRecPtrIsInvalid() macro
Date: Tue, 2 Dec 2025 08:44:28 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <aQ2O99S+VjEZSf3/@ip-10-97-1-34.eu-west-3.compute.internal>
	<[email protected]>
	<[email protected]>
	<aRw2/gV/[email protected]>
	<[email protected]>
	<[email protected]>

On 01.12.25 08:14, Bertrand Drouvot wrote:
> Hi,
> 
> On Tue, Nov 18, 2025 at 04:54:32PM +0100, Peter Eisentraut wrote:
>> I mean, some people like writing if (!foo) and some like writing if
>> (foo == NULL), but we're not going to legislate one
>> over the other.
> 
> Agree. Out of curiosity, I searched for pointers and literal zero comparisons
> or assignments (with [1]) and found 6 of them.
> 
> While literal zero is technically correct, NULL is the semantically appropriate
> choice for pointers.
> 
> PFA a patch to fix those 6.

committed (required pgindent)

view thread (47+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Consistently use the XLogRecPtrIsInvalid() macro
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox