Re: Replace l337sp34k in comments. - Mailing list pgsql-hackers

From Gavin Flower
Subject Re: Replace l337sp34k in comments.
Date
Msg-id 73690a4f-abd7-3452-9aea-397078a6b0f9@archidevsys.co.nz
Whole thread Raw
In response to Re: Replace l337sp34k in comments.  (Geoff Winkless <pgsqladmin@geoff.dj>)
List pgsql-hackers
On 30/07/21 8:05 pm, Geoff Winkless wrote:
> On Thu, 29 Jul 2021 at 22:46, Gavin Flower
> <GavinFlower@archidevsys.co.nz> wrote:
>> Though in code, possibly it would be better to just use 'up-to-date' in
>> code for consistency and to make the it easier to grep?
> If it's causing an issue, perhaps using a less syntactically
> problematic synonym like "current" might be better?
>
> :)
>
> Geoff

On thinking further...

The word 'current' means different things in different contexts. If I 
refer to my current O/S it means the one I'm using now, but it may not 
be current.  The second use of 'current' is the meaning you are thinking 
of, but the first is not. Since people reading documented code are 
focused on understanding technical aspects, they may miss this subtlety.

I'm aware that standardisation may meet with some resistance, but being 
consistent might reduce the conceptual impedance when reading the code.  
I'm just trying to reduce the potential for confusion.


Cheers,
Gavin




pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Use generation context to speed up tuplesorts
Next
From: Jeff Davis
Date:
Subject: Re: alter table set TABLE ACCESS METHOD