Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106338
MIME-Version: 1.0
References: <CAF+90c_Ctjja=8fR-uBWL1wDxZge771yMujMhaR_R2seKXciYw@mail.gmail.com>
 <CAF+90c8JhV6-aQrsvW8u_xGB-wHmyObEU1Chd64J+x3tkKogQQ@mail.gmail.com>
 <9ADC8994-9D3C-4810-A2DB-6FB81D513098@gmail.com> <CABdc3WqxvucnCk7rd-Y2YuNn_dCvh5atNagwCqo8gp9NjMt_aQ@mail.gmail.com>
 <CANS-=pcp=-t4-cEHK8vbuNAaMBLSjmoL94h-TXKtHm0v8Ptkqg@mail.gmail.com>
In-Reply-To: <CANS-=pcp=-t4-cEHK8vbuNAaMBLSjmoL94h-TXKtHm0v8Ptkqg@mail.gmail.com>
Date: Tue, 30 Jul 2019 09:48:26 +0100
Message-ID: <CALKiJKorD5xayU1QYtd_XMEz7Zkx+etWs3k3DGZS3O9zPnk7mQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000002cf417058ee213f5"
Subject: Re: [PHP-DEV] Re: [RFC] Namespace-scoped declares, again
From: rowan.collins@gmail.com (Rowan Collins)

--0000000000002cf417058ee213f5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

 On Tue, 30 Jul 2019 at 09:12, Micha=C5=82 Brzuchalski <michal@brzuchalski.=
com>
wrote:

> 1) Packages should be non-hierarchical. Perhaps most simply a package nam=
e
>> could have exactly two parts, like in composer, so it's clear that there=
 is
>> no implied relationship between two packages.
>>
>
> IMO this would create a lot of problems cause name in Composer Package
> doesn't reflect used namespace declared in autoload
>


I'm not saying the package name has to match the composer name, just that
the format might be similar; and I explicitly left the question open of how
package names would relate to namespaces. It might be sensible to align the
package/module name with one or other of the existing two naming schemes,
but it's certainly not essential; names in Composer are essentially
arbitrary anyway, not visible at all at run-time.


On Tue, 30 Jul 2019 at 09:20, Lynn <kjarli@gmail.com> wrote:

> Would it be an idea to first establish the concept of a package within
> PHP, rather than deducting it based off a namespace? If packages would be=
 a
> thing in PHP, other than just a namespace, package private could also be
> implemented as visibility modifier for inheritance and class visibility.
>


I think there's some confusion here, because establishing the concept of a
package as separate from a namespace is exactly what I proposed.

Here's a previous message (technically in the same thread, but from 18
months ago) where I also mentioned class visibility:
https://externals.io/message/101323#101390


Regards,
--=20
Rowan Collins
[IMSoP]

--0000000000002cf417058ee213f5--