From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: "Cannot" vs "could not"
Date: Thu, 19 Mar 2020 12:37:22 -0400
Message-ID: <20200319163722.GD2571@momjian.us> (raw)
In-Reply-To: <25965.1584634055@sss.pgh.pa.us>
References: <20200319155704.GC2571@momjian.us>
<25965.1584634055@sss.pgh.pa.us>
On Thu, Mar 19, 2020 at 12:07:35PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > We use "cannot" and "could not" quite often in source code and error
> > messages:
>
> Yup.
>
> > Is there any sense that we should have more consistency in our message
> > wording?
>
> There is specific guidance about it in our error message style guide:
>
> https://www.postgresql.org/docs/devel/error-style-guide.html
>
> (see under "Present vs. Past Tense"). I believe we largely conform
> to that guideline, though of course exceptions sneak in from time
> to time.
Oh, good. I remember we discussed this in the past, but didn't realize
we had written it down. Thanks.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EnterpriseDB https://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
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: pgsql-docs@postgresql.org
Cc: bruce@momjian.us, tgl@sss.pgh.pa.us
Subject: Re: "Cannot" vs "could not"
In-Reply-To: <20200319163722.GD2571@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox