Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124659
Message-ID: <630b4e1e452d40e5f807d155cf97a10550ee4dd5.camel@ageofdream.com>
Subject: Re: [PHP-DEV] Should PHP reserve a namespace for built-in classes?
To: internals@lists.php.net
Date: Sat, 27 Jul 2024 19:11:01 -0400
In-Reply-To: <098864EF-9D75-417A-82DC-105082DA3A23@gmail.com>
References: <76559a9cd5eca4bc6799ed9612ce15c28cd7cb0a.camel@ageofdream.com>
	 <95f6046a-4acf-4f8a-a850-a23650c0c6b3@bastelstu.be>
	 <927705b0404e70b0f0ade4a3354b2598d7c112f9.camel@ageofdream.com>
	 <86b7e340-6ca9-4b3c-af0a-a5c2d1ee68c3@bastelstu.be>
	 <ab4c1bbc8b316d81cfcf22e416f38e408745f89e.camel@ageofdream.com>
	 <098864EF-9D75-417A-82DC-105082DA3A23@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.46.4-2 
Precedence: bulk
MIME-Version: 1.0
From: lists@ageofdream.com (Nick Lockheart)



On Sun, 2024-07-28 at 00:48 +0200, Claude Pache wrote:
>=20
> For the case of functions (and constants) in the global namespace,
> there was an RFC on the subject about 4 years ago, which has been
> declined; see:=C2=A0https://wiki.php.net/rfc/use_global_elements=C2=A0and=
 the
> discussion threads referenced at the bottom of that page.


The top of the RFC correctly outlines the problem; a problem that still
exists. Maybe the proposed solution wasn't the best approach, but it
still remains an issue: Classes that are built-in to PHP are and will
cause naming collisions with developer code.

I think the C++ approach is simple and elegant:

    using std::string;

The C++ standard library will never collide with user code as you ask
for it when you want it.