| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Undesirable entries in typedefs list |
| Date: | 2018-03-24 17:29:19 |
| Message-ID: | 20180324172919.axixlwl2itsk2yx3@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2018-03-24 13:25:34 -0400, Tom Lane wrote:
> (2) "abs", "boolean", "iterator", "other", "pointer", "reference",
> "string", and "type" all now are listed as typedef names.
>
> It's probably okay to treat "boolean" as a typedef, but all those others
> are complete disasters. Anyone know where they're coming from?
Semi informed theory: LLVM? I think I'd configured one of the LLVM
animals to collect typedefs, but that might have been a bad idea...
> As for "bool", we could probably deal with that most reliably by
> having pgindent add it as a special case. Maybe we could get it
> back in there by having some trailing-edge buildfarm member
> contribute typedefs, but that seems like a solution with a rather
> limited half-life.
Could we combine the list of typedefs with one manually maintained
in-tree?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-03-24 17:34:45 | Re: Undesirable entries in typedefs list |
| Previous Message | Tom Lane | 2018-03-24 17:25:34 | Undesirable entries in typedefs list |