Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121164
MIME-Version: 1.0
Date: Thu, 28 Sep 2023 22:19:47 +0200
Message-ID: <CAH5C8xXfdYEHeoRBi07ecaDQJQ8VxoXMJRiaZ=yw9kTqQaNQ0w@mail.gmail.com>
To: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000004d083c060671081f"
Subject: proc_open() resource to opaque object migration
From: kocsismate90@gmail.com (=?UTF-8?B?TcOhdMOpIEtvY3Npcw==?=)

--0000000000004d083c060671081f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Everyone,

I'm writing in connection with a question coming up lately during the
"resource to opaque object migration" project (
https://github.com/php/php-tasks/issues/6) which we have been working on
for quite a long while.

During the review of my PR migrating the resource returned by proc_open()
to an object (https://github.com/php/php-src/pull/12098), it quickly became
evident that there was no consensus about the new class name, since the
originally proposed "Process" name has a non-negligible BC break likelihood=
.

That's why we should find the best class name in accordance with Nikita's
namespace naming convention RFC (
https://wiki.php.net/rfc/namespaces_in_bundled_extensions). Even though my
PR currently implements "Standard\Process", this name is not a good
candidate according to the policy:

Because these extensions combine a lot of unrelated or only tangentially
> related functionality, symbols should not be namespaced under the Core,
> Standard or Spl namespaces. Instead, these extensions should be considere=
d
> as a collection of different components, and should be namespaced accordi=
ng
> to these.


Does anyone have a good suggestion?

Thanks,
M=C3=A1t=C3=A9

--0000000000004d083c060671081f--