Re: "Cannot" vs "could not" - Mailing list pgsql-docs

From Bruce Momjian
Subject Re: "Cannot" vs "could not"
Date
Msg-id 20200319163722.GD2571@momjian.us
Whole thread Raw
In response to Re: "Cannot" vs "could not"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-docs
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 +



pgsql-docs by date:

Previous
From: Tom Lane
Date:
Subject: Re: "Cannot" vs "could not"
Next
From: Bruce Momjian
Date:
Subject: Re: explanation for random_page_cost is outdated