Re: Replace l337sp34k in comments.

From: Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>
To: Geoff Winkless <pgsqladmin(at)geoff(dot)dj>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Replace l337sp34k in comments.
Date: 2021-07-29 21:46:59
Message-ID: 1f052c95-850d-a90f-9908-552030505c6b@archidevsys.co.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 30/07/21 12:51 am, Geoff Winkless wrote:
> On Thu, 29 Jul 2021 at 11:22, Andrew Dunstan <andrew(at)dunslane(dot)net
> <mailto:andrew(at)dunslane(dot)net>> wrote:
>
> Personally, I would have written this as just "up to date", I don't
> think the hyphens are required.
>
> FWIW Mirriam-Webster and the CED suggest "up-to-date" when before a
> noun, so the changes should be "up-to-date answer" but "are up to date".
>
> https://dictionary.cambridge.org/dictionary/english/up-to-date
> <https://dictionary.cambridge.org/dictionary/english/up-to-date>
>
> Geoff

That 'feels' right to me.

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?

As a minor aside: double quotes should be used for speech and single
quotes for quoting!

Cheers,
Gavin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2021-07-29 22:11:03 Re: pg_upgrade does not upgrade pg_stat_statements properly
Previous Message Daniel Gustafsson 2021-07-29 21:30:53 Re: Doc: Fixed the result of the bit_count example