Re: pgsql: Default to hidden visibility for extension libraries where possi - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pgsql: Default to hidden visibility for extension libraries where possi
Date
Msg-id 1697006.1658326141@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Default to hidden visibility for extension libraries where possi  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, Jul 20, 2022 at 9:39 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> ISTM that a comment pointing out that the functions marked PGDLLEXPORT
>> are meant to be externally accessible should be sufficient.

> The name PGDLLEXPORT is actually slightly misleading, now, because
> there's no longer anything about it that is specific to DLLs.

True, but the mess of changing it seems to outweigh any likely clarity
gain.  As long as there's adequate commentary about what it means,
I'm okay with the existing naming.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pgsql: Default to hidden visibility for extension libraries where possi
Next
From: Amit Langote
Date:
Subject: Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size