Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111901
MIME-Version: 1.0
References: <CAJpLVh0K0Mkqa2RP9DLWNXbZJGqhrvJ4CTOWvAkz-7iGENWjYg@mail.gmail.com>
 <CABdc3WomjqP3mp37q2H=imF526WshvSr7SFqa-VFbjqRd4BrNw@mail.gmail.com> <CAJpLVh1H96fu6m63K71e9yyYKrDWbpVWtjC+Pj24+F1eqYE4Fw@mail.gmail.com>
In-Reply-To: <CAJpLVh1H96fu6m63K71e9yyYKrDWbpVWtjC+Pj24+F1eqYE4Fw@mail.gmail.com>
Date: Fri, 18 Sep 2020 11:23:47 +0200
Message-ID: <CAJpLVh2oGuau618S3vtPAi=VaaK3rVALk-POH6AL=Ew_qpa7yw@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000008ce8fe05af930f9a"
Subject: Fwd: [PHP-DEV] Namespace-private class properties
From: olleharstedt@gmail.com (=?UTF-8?Q?Olle_H=C3=A4rstedt?=)

--0000000000008ce8fe05af930f9a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

---------- Forwarded message ---------
From: Olle H=C3=A4rstedt <olleharstedt@gmail.com>
Date: Fri, 18 Sep 2020, 11:23
Subject: Re: [PHP-DEV] Namespace-private class properties
To: Micha=C5=82 Marcin Brzuchalski <michal.brzuchalski@gmail.com>




On Fri, 18 Sep 2020, 06:15 Micha=C5=82 Marcin Brzuchalski, <
michal.brzuchalski@gmail.com> wrote:

> Hi Olle,
>
> czw., 17 wrz 2020, 14:28 u=C5=BCytkownik Olle H=C3=A4rstedt <olleharstedt=
@gmail.com>
> napisa=C5=82:
>
>> (NB: This idea is NOT about namespace visibility for classes, interfaces
>> or
>> traits (already discussed here:
>> https://wiki.php.net/rfc/namespace-visibility).
>> It's about adding a *new* visibility qualifier, call it "internal", to
>> make properties
>> private inside a namespace. The purpose is to make composition less
>> fragile by not
>> exposing more than necessary.)
>>
>> (NB: This feature exists in Swift, described here:
>> https://docs.swift.org/swift-book/LanguageGuide/AccessControl.html)
>>
>> We have public, protected and private. Since PHP has no module system, w=
e
>> have no qualifier to mark a class property as "private for this module".
>> One solution to this could be to add a new qualifier "internal", to make
>> properties public within the current namespace.
>>
>> Use-cases:
>>
>> * Split data and behaviour into different files and classes
>> * Safely skip getters and setters without risk of properties being abuse=
d
>> by client code
>>
>> Tiny example:
>>
>> ```
>> namespace App\User;
>> class User {
>>   internal $username;
>>   internal $password;
>> }
>>
>> namespace App\User\Services;
>> class ProcessUser {
>>   // Child namespace has access to internal properties,
>>   // but App\ has not.
>> }
>> ```
>>
>> Possible?
>>
>
> I say it's not possible. There is no control over use when you pass
> reference. It is easy to load class in "child" namespace which extracts
> references and pass them wherever.
>
> Keep in mind that namespace on PHP is just a class/funtion/const name
> prefix and nothing more nothing less. While it may work in languages with
> support of modules in PHP there is no such thing.
>
> Cheers,
> Micha=C5=82 Marcin Brzuchalski
>

Hm, does that mean that PHP doesn't know which namespace it's in in any
given moment? Is there no "context" tracking in the compiler?

>

--0000000000008ce8fe05af930f9a--