Re: "Cannot" vs "could not"

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org>
Subject: Re: "Cannot" vs "could not"
Date: 2020-03-19 16:37:22
Message-ID: 20200319163722.GD2571@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Thu, Mar 19, 2020 at 12:07:35PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)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 +

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2020-03-19 20:56:46 Re: explanation for random_page_cost is outdated
Previous Message Tom Lane 2020-03-19 16:07:35 Re: "Cannot" vs "could not"