Re: do {} while (0) nitpick
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: David Steele <david@pgmasters.net>, Bruce Momjian <bruce@momjian.us>,
John Naylor <john.naylor@2ndquadrant.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2020-05-06T19:24:40Z
Lists: pgsql-hackers
Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes: > I tried this out with ppport.h from perl 5.30.2 which is what's on my > Fedora 31 workstation. It compiled fine, no warnings and the tests all > ran fine. > So we could update it. I'm just not sure there would be any great > benefit from doing so until we want to use some piece of perl API that > postdates 5.11.2, which is where our current file comes from. Yeah, perhaps not. Given our general desire not to break old toolchains, it might be a long time before we want to require any new Perl APIs. > I couldn't actually find an instance of the offending pattern in either > version of pport.h. What am I overlooking? My script was looking for any macro ending with ';', so it found these: #define START_MY_CXT static my_cxt_t my_cxt; # define XCPT_TRY_END JMPENV_POP; # define XCPT_TRY_END Copy(oldTOP, top_env, 1, Sigjmp_buf); Those don't seem like things we'd use directly, so it's mostly moot. BTW, I looked around and could not find a package-provided ppport.h at all on my Red Hat systems. What package is it in? regards, tom lane
Commits
-
Get rid of trailing semicolons in C macro definitions.
- ad80d3ea27b1 9.5.22 landed
- a8df87d8638c 9.6.18 landed
- a2098b60216c 11.8 landed
- 49718aa9ee5e 10.13 landed
- c08da32f133b 12.3 landed
- 0da06d9faf9e 13.0 landed