Re: Move NON_EXEC_STATIC from c.h

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Move NON_EXEC_STATIC from c.h
Date: 2022-08-23 19:13:20
Message-ID: bfd3570c-6e96-e728-fd8a-16ed2d5505f5@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 16.08.22 15:50, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)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.

Attachment Content-Type Size
v2-0001-Move-NON_EXEC_STATIC-from-c.h-to-postgres.h.patch text/plain 2.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan S. Katz 2022-08-23 19:31:06 Re: SQL/JSON features for v15
Previous Message Robert Haas 2022-08-23 18:58:32 Re: replacing role-level NOINHERIT with a grant-level option