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

From Andres Freund
Subject Re: pgsql: Default to hidden visibility for extension libraries where possi
Date
Msg-id 6AB9B363-8FA3-4641-B9B5-9B3427F5E742@anarazel.de
Whole thread Raw
In response to Re: pgsql: Default to hidden visibility for extension libraries where possi  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Re: pgsql: Default to hidden visibility for extension libraries where possi
List pgsql-hackers
Hi,

On July 20, 2022 3:54:03 PM GMT+02:00, Robert Haas <robertmhaas@gmail.com> wrote:
>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.

How so? Right now it's solely used for making symbols in DLLs as exported?

Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size
Next
From: Aleksander Alekseev
Date:
Subject: Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.