From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Harmonizing pg_bsd_indent parameter names |
Date: | 2024-06-12 21:33:34 |
Message-ID: | 1608893.1718228014@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> Attached patch harmonizes pg_bsd_indent's function parameter names, so
> that they match the names used in corresponding function definitions.
Hmm, these aren't really harmonizing inconsistencies, but overruling
somebody's style decision to leave parameter names out of the extern
declarations. That's a style I don't like personally, but some do.
> I have been putting this off because I wasn't sure that the policy
> should be the same for pg_bsd_indent. Is there any reason to think
> that this will create more work down the line? It seems like it might,
> due to some kind of need to keep pg_bsd_indent's consistent with
> upstream BSD indent.
We are, at least in theory, trying to stay within hailing distance
of the upstream; that's the primary reason why we've not touched
the indentation style of pg_bsd_indent itself. Still, two lines
is not going to make much of a difference in whether patches can
be passed back and forth (whereas reindentation would kill that
somewhat thoroughly).
Anyway, after chewing on it for a few minutes, no objection here.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sutou Kouhei | 2024-06-12 21:40:01 | Re: RFC: adding pytest as a supported test framework |
Previous Message | Nathan Bossart | 2024-06-12 21:32:54 | Re: Harmonizing pg_bsd_indent parameter names |