| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Piotr Stefaniak <postgres(at)piotr-stefaniak(dot)me> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_bsd_indent - improvements around offsetof and sizeof |
| Date: | 2016-05-25 20:07:34 |
| Message-ID: | 20160525200734.nuv4ppfbvzj6odeu@alap3.anarazel.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-05-25 22:01:53 +0200, Piotr Stefaniak wrote:
> On 2016-05-25 21:13, Tom Lane wrote:
> > I'd love to see a fix for its brain damage around function pointer typedef formatting, too.
>
> Show me a few examples and I'll look into it.
>
> > I'm excited about this too, not least because it suggests that maybe bsdindent isn't quite as opaque as it appears.
>
> It's old, hacked on many times over the past few decades and historically
> just a band-aid rather than something designed from the ground up, so it's
> not easy to work with. Which is why I think that a newer tool (like
> ClangFormat) should be considered as a replacement for pg_bsd_indent.
FWIW, I looked at using clang-format at some point, and it looked like
it'd be a number of additional options to make it work for our case
without changing the code layout too much. There seemed limited
enthusiasm from the authors about accepting relevant options.
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-05-25 20:32:57 | Re: Changed SRF in targetlist handling |
| Previous Message | Piotr Stefaniak | 2016-05-25 20:01:53 | Re: pg_bsd_indent - improvements around offsetof and sizeof |