Re: Replace l337sp34k in comments.
Gavin Flower <gavinflower@archidevsys.co.nz>
From: Gavin Flower <GavinFlower@archidevsys.co.nz>
To: Geoff Winkless <pgsqladmin@geoff.dj>
Cc: Andrew Dunstan <andrew@dunslane.net>, Peter Smith
<smithpb2250@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-07-30T21:15:59Z
Lists: 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
Commits
-
Clarify some comments making use of leetspeak term "up2date"
- 7b7fbe1e8bb4 15.0 landed
-
doc: restore intentional typo
- 8a47b775a16f 13.0 cited
-
Introduce logical decoding.
- b89e151054a0 9.4.0 cited