Re: pgindent vs dtrace on macos - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: pgindent vs dtrace on macos
Date
Msg-id B498B70E-C1D7-474B-871B-8B2C35F840FB@yesql.se
Whole thread Raw
In response to Re: pgindent vs dtrace on macos  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgindent vs dtrace on macos  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> On 21 Sep 2020, at 20:55, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Oh wait, I forgot about the fmgrprotos.h discrepancy.
>
> I wrote:
>> It strikes me that a low-cost workaround would be to rename these
>> C functions.  There's no law that their C names must match the
>> SQL names.
>
> Here's a proposed patch to fix it that way.

+1 on this patch.  Do you think it's worth adding a note about this in the
documentation to save the next one staring at this a few minutes?  Something
along the lines of:

--- a/src/tools/pgindent/README
+++ b/src/tools/pgindent/README
@@ -110,6 +110,9 @@ Sometimes, if pgindent or perltidy produces odd-looking output, it's because
 of minor bugs like extra commas.  Don't hesitate to clean that up while
 you're at it.

+If an exported function shares a name with a typedef, the header file with the
+prototype can get incorrect spacing for the function.
+

cheers ./daniel


pgsql-hackers by date:

Previous
From: Andrey Lepikhov
Date:
Subject: Re: Global snapshots
Next
From: "Hou, Zhijie"
Date:
Subject: RE: Use appendStringInfoString and appendPQExpBufferStr where possible