Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110046
To: php internals <internals@lists.php.net>
Message-ID: <72545a0e-2a84-855f-a9a9-af872e4bc2f9@gmx.de>
Date: Wed, 6 May 2020 17:43:32 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
Subject: Making IPC_PRIVATE available to userland
From: cmbecker69@gmx.de ("Christoph M. Becker")

Hi all,

the POSIX standard doesn't mandate that IPC_PRIVATE has any particular
value; in practise it is often (maybe always) zero, but I think the
constant is important enough to deserve its own PHP userland constant.
It would be useful for shmop_open(), shm_attach() and sem_get(), but
these three functions belong to three different extensions (shmop,
sysvshm, sysvsem), so it is not clear where to define the constant, and
how to name it.

My first thought was to define `PHP_IPC_PRIVATE` in main.c, but Nikita
had reasonable objections to expose the constant from core.  I came up
with a somewhat doubtful alternative[1]; a maybe even worse alternative
would be to define three separate constants.

Has anybody an idea how to solve that?  Of course, you could also
comment on <https://github.com/php/php-src/pull/5527> directly.

[1]
<https://github.com/php/php-src/pull/5527/commits/a33d2f3921e53810873e6cbb7856234e24520ab8>

Thanks,
Christoph