Re: Typos in the code and README

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Typos in the code and README
Date: 2024-04-12 20:55:16
Message-ID: ZhmftCSDVEw3ygoP@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 11, 2024 at 03:37:00PM +0200, Daniel Gustafsson wrote:
> On 11 Apr 2024, at 15:29, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
>
> On Fri, 12 Apr 2024, 1:05 am Daniel Gustafsson, <daniel(at)yesql(dot)se> wrote:
>
> Now that the tree has settled down a bit post-freeze I ran some tooling
> to
> check spelling. I was primarily interested in docs and README* which
> were
> mostly free from simply typos, while the code had some in various
> comments and
> one in code. The attached fixes all that I came across (not
> cross-referenced
> against ongoing reverts or any other fixup threads but will be before
> pushing
> of course).
>
>
> I see you've corrected "iif" to "if". It should be "iff".
>
>
> Gotcha, will fix. I opted for "if" due to recent threads where the use of
> "iff" was discouraged due to not being commonly known, but that was in doc/ and
> not code comments.

I actually agree "iff" is just not clear enough. "Iff" stands for "if
and only if" and maybe should be spelled out that way.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Only you can decide what is important to you.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2024-04-12 20:58:22 Re: Typos in the code and README
Previous Message Erik Wienhold 2024-04-12 20:15:08 Re: CASE control block broken by a single line comment