Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123182
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Mime-Version: 1.0 (1.0)
Date: Tue, 23 Apr 2024 22:47:37 +0930
Message-ID: <FCC86854-A066-4BD0-965C-DEFAF2728242@koalephant.com>
References: <1cc7c609-0c12-4050-b792-2f4077a6ae69@scriptfusion.com>
In-Reply-To: <1cc7c609-0c12-4050-b792-2f4077a6ae69@scriptfusion.com>
Subject: Re: [PHP-DEV] PDO subclass names
To: Bilge <bilge@scriptfusion.com>, internals@lists.php.net
From: php-lists@koalephant.com (Stephen Reay)


Sent from my iPhone

> On 23 Apr 2024, at 22:35, Bilge <bilge@scriptfusion.com> wrote:
> =EF=BB=BFOn 23/04/2024 10:25, Stephen Reay wrote:
>> The argument that "Client" is meaningless becomes pretty moot when you re=
alise that you can import a *namespace* and use it relatively, if you so wis=
h:
>>=20
>> ```
>> import MyLib\HTTP;
>>=20
>> $a =3D new HTTP\Client(...);
>> ```
>=20
> Hi Stephen,
>=20
> Granted, but I also believe the user can and should have the reasonable ex=
pectation that they can work comfortably (without conflicts or aliases) usin=
g leaf (class) names exclusively.
>=20
> Kind regards,
> Bilge

I'm sorry but I think you've missed the entire point of namespaces if you wa=
nt class names to all be universally unique without their namespace componen=
t.

The referenced RFC gives clear examples of how a class with a prefix would b=
e converted to a namespace and class.=20