Re: assorted code cleanup
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Michael Paquier <michael.paquier@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2017-09-05T19:32:27Z
Lists: pgsql-hackers
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes: > Do you mean specifically the hook variables, or any function pointers? > I can see your point in the above case, but for example here > - if ((*tinfo->f_lt) (o.upper, c.upper, flinfo)) > + if (tinfo->f_lt(o.upper, c.upper, flinfo)) > I think there is no loss of clarity and the extra punctuation makes it > more complicated to read. At one time there were C compilers that only accepted the former syntax. But we have already occurrences of the latter in our tree, and no one has complained, so I think that's a dead issue by now. I do agree with the idea that we should use the * notation in cases where the reader might otherwise think that a plain function was being invoked, ie I don't like some_function_pointer(args); Even if the compiler isn't confused, readers might be. But in the case of structname->pointerfield(args); it's impossible to read that as a plain function call, so I'm okay with dropping the extra punctuation there. regards, tom lane
Commits
-
Reduce excessive dereferencing of function pointers
- 1356f78ea933 11.0 landed