Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129148
Precedence: list
MIME-Version: 1.0
References: <e21b1992-d426-46cd-b86a-6d6a5844c934@app.fastmail.com>
In-Reply-To: <e21b1992-d426-46cd-b86a-6d6a5844c934@app.fastmail.com>
Date: Sat, 8 Nov 2025 13:30:05 +0000
Message-ID: <CAGBsUreR+ROHpyp5h-_gfH7m5UC-Yw9usKyzrn6aWRb6satpAA@mail.gmail.com>
Subject: Re: [PHP-DEV] RFC: Namespace-Scoped Visibility for Methods and Properties
To: Rob Landers <rob@bottled.codes>
Cc: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: tekiela246@gmail.com (Kamil Tekiela)

On Sat, 8 Nov 2025 at 12:44, Rob Landers <rob@bottled.codes> wrote:
>
> Hello Internals,
>
> I=E2=80=99d like to introduce an RFC for discussion: https://wiki.php.net=
/rfc/namespace_visibility which proposes a new visibility modifier: private=
(namespace).
>
> This idea has appeared several times in previous threads but never progre=
ssed to a formal proposal (from what I could find). My hope is that with de=
fined semantics, examples, and implementation details, we can evaluate it p=
roperly and see whether there=E2=80=99s support for moving forward. Feedbac=
k is very welcome.
>
> Sincerely,
>
> Rob Landers

I like the idea except for the name. Why not use the internal keyword
like C# does?