Re: Move NON_EXEC_STATIC from c.h
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2022-08-23T19:13:20Z
Lists: pgsql-hackers
Attachments
- v2-0001-Move-NON_EXEC_STATIC-from-c.h-to-postgres.h.patch (text/plain) patch v2-0001
On 16.08.22 15:50, Tom Lane wrote: > Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes: >> Looking to tidy up c.h a bit, I think the NON_EXEC_STATIC #define >> doesn't need to be known globally, and it's not related to establishing >> a portable C environment, so I propose to move it to a more localized >> header, such as postmaster.h, as in the attached patch. > > Hmm, postgres.h seems like a better choice, since in principle any > backend file might need this. This arrangement could require > postmaster.h to be included just for this macro. I picked postmaster.h because the other side of the code, where the no-longer-static symbols are used, is in postmaster.c. But postgres.h is also ok. > Also, the macro was severely underdocumented already, and I don't > find "no comment at all" to be better. Can't we afford a couple > of lines of explanation? Here is a new patch with more comments.
Commits
-
Move NON_EXEC_STATIC from c.h to postgres.h
- 2059c5e3b065 16.0 landed