From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "'Tom Lane *EXTERN*'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Add PGDLLEXPORT to PG_FUNCTION_INFO_V1 |
Date: | 2016-10-12 14:54:49 |
Message-ID: | A737B7A37273E048B164557ADEF4A58B5393038C@ntex2010a.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> I'm okay with adding PGDLLEXPORT to the extern, but we should update
> that comment to note that it's not necessary with any of our standard
> Windows build processes. (For that matter, the comment fails to explain
> why this macro is providing an extern for the base function at all...)
Here is a patch for that, including an attempt to improve the comment.
Yours,
Laurenz Albe
Attachment | Content-Type | Size |
---|---|---|
0001-Add-PGDLLEXPORT-to-PG_FUNCTION_INFO_V1.patch | application/octet-stream | 1.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2016-10-12 15:00:50 | Re: Renaming of pg_xlog and pg_clog |
Previous Message | Peter Eisentraut | 2016-10-12 14:49:01 | Re: Remove "Source Code" column from \df+ ? |