Re: pgindent && weirdness
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
Michael Paquier <michael@paquier.xyz>, Pg Hackers <pgsql-hackers@lists.postgresql.org>, Piotr Stefaniak <postgres@piotr-stefaniak.me>
Date: 2020-05-15T22:05:38Z
Lists: pgsql-hackers
Attachments
- 0001-Fix-formatting-of-macros-that-take-types.patch (text/x-patch) patch 0001
- 0001-Fix-formatting-of-IsA-and-similar-macros.patch (text/x-patch) patch 0001
On Tue, Feb 18, 2020 at 12:42 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > Thomas Munro <thomas.munro@gmail.com> writes: > > Another problem is that there is one thing in our tree that looks like > > a non-cast under the new rule, but it actually expands to a type name, > > so now we get that wrong! (I mean, unpatched indent doesn't really > > understand it either, it thinks it's a cast, but at least it knows the > > following * is not a binary operator): > > > - STACK_OF(X509_NAME) *root_cert_list = NULL; > > + STACK_OF(X509_NAME) * root_cert_list = NULL; > > > That's a macro from an OpenSSL header. Not sure what to do about that. > > If we get that wrong, but a hundred other places look better, > I'm not too fussed about it. Here's the patch I propose to commit to pg_bsd_indent, if the repo lets me, and here's the result of running it on the PG tree today. I suppose the principled way to fix that problem with STACK_OF(x) would be to have a user-supplied list of function-like-macros that expand to a type name, but I'm not planning to waste time on that.
Commits
-
Run pgindent with new pg_bsd_indent version 2.1.1.
- fa27dd40d5c5 13.0 landed
-
Final pgindent run with pg_bsd_indent version 2.1.
- e02ad575d8ab 13.0 landed