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: Making C function declaration parameter names consistent with corresponding definition names |
Date: | 2022-09-17 18:26:25 |
Message-ID: | 29327.1663439185@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:
> Several files from src/timezone and from src/backend/regex make use of
> unnamed parameters in function declarations. It wouldn't be difficult
> to fix everything and call it a day, but I wonder if there are any
> special considerations here. I don't think that Henry Spencer's regex
> code is considered vendored code these days (if it ever was), so that
> seems clear cut. I'm less sure about the timezone code.
Yeah, bringing the regex code into line with our standards is fine.
I don't really see a reason not to do it with the timezone code
either, as long as there aren't too many changes there. We are
carrying a pretty large number of diffs from upstream already.
(Which reminds me that I need to do another update pass on that
code soon. Not right now, though.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2022-09-17 18:36:48 | Re: Making C function declaration parameter names consistent with corresponding definition names |
Previous Message | Peter Geoghegan | 2022-09-17 18:05:09 | Re: Making C function declaration parameter names consistent with corresponding definition names |