Re: Fixing MSVC's inability to detect elog(ERROR) does not return

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fixing MSVC's inability to detect elog(ERROR) does not return
Date: 2025-09-17 04:25:36
Message-ID: CAApHDvr71WXZgLYPLNC0zUsNufYhBer4rYiHQF_-jQ4iDKBRsg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 17 Sept 2025 at 16:03, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> > On Wed, 3 Sept 2025 at 23:32, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
> >> Btw., I think we should stick to the *_p() naming (for "predicate", I
> >> think) for compiler-intrinsic-affiliated functions/macros that report
> >> boolean results.
>
> > I didn't know what the _p suffix was meant to indicate. Do you have a
> > link which states that it's for "predicate"?
>
> It absolutely stands for "predicate". That's an ancient Lisp-ism.
> Here's the first link I found with some quick googling:
>
> https://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node69.html

Thanks for the confirmation. I'm happy enough to leave the _p in
there, but at the same time, I don't see the particular reason to
follow some ancient Lisp rule. Maybe I'm in the minority, having never
programmed in Lisp.

Anyway, at least the justification for it is in the archives now. Thanks.

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2025-09-17 04:27:22 Re: DOCS: What SGML markup to use for user objects like tables, columns, etc?
Previous Message Tom Lane 2025-09-17 04:02:56 Re: Fixing MSVC's inability to detect elog(ERROR) does not return