public inbox for [email protected]  
help / color / mirror / Atom feed
From: Bruce Momjian <[email protected]>
To: Daniel Gustafsson <[email protected]>
Cc: David Rowley <[email protected]>
Cc: PostgreSQL Developers <[email protected]>
Subject: Re: Typos in the code and README
Date: Fri, 12 Apr 2024 16:55:16 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<CAApHDvpHJzUkjShGSo896ed3YmN89+2iJNRQ6uCafHvu0c5KEQ@mail.gmail.com>
	<[email protected]>

On Thu, Apr 11, 2024 at 03:37:00PM +0200, Daniel Gustafsson wrote:
>     On 11 Apr 2024, at 15:29, David Rowley <[email protected]> wrote:
> 
>     On Fri, 12 Apr 2024, 1:05 am Daniel Gustafsson, <[email protected]> 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  <[email protected]>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.






view thread (5+ 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]
  Subject: Re: Typos in the code and README
  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