Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107960
Message-ID: <42078B8B-D8A7-4C6A-8A6F-17C6F69498E0@newclarity.net>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_435E4480-A6E0-4187-A521-F9F92B0BF9AD"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Thu, 2 Jan 2020 11:52:43 -0500
In-Reply-To: <5e0d723f.1c69fb81.e2ae8.24e2SMTPIN_ADDED_MISSING@mx.google.com>
Cc: Mark Randall <marandall@php.net>
To: PHP internals <internals@lists.php.net>
References: <DM5PR07MB3067B7578E3F04C5A20A221AF9210@DM5PR07MB3067.namprd07.prod.outlook.com>
 <5e0d723f.1c69fb81.e2ae8.24e2SMTPIN_ADDED_MISSING@mx.google.com>
Subject: Re: [PHP-DEV] Re: [RFC] "use global functions/consts" statement
From: mike@newclarity.net (Mike Schinkel)

--Apple-Mail=_435E4480-A6E0-4187-A521-F9F92B0BF9AD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> On Jan 1, 2020, at 11:31 PM, Mark Randall <marandall@php.net> wrote:
> In future, I think the optimal solution is opt-in deprecating fallback =
to the root namespace using a declare. We might eventually benefit from =
versioned "libraries" of functions that can be imported in one command =
which would solve many-a-future-problem by itself.

+1 to that. =20

Especially if there is a mechanism to define functions from other =
people's code to be included in those "libraries", such as the functions =
in the WordPress API.

> Id like to see nikic/scalar_objects added to the core in 8.0, that =
would offer non-procedural (and therefore non-namespaced) access to many =
of the most common global functions (strings, arrays etc). In turn, that =
would allow developers to limit the number of use \... statements.

And +1000 to that!

-Mike


--Apple-Mail=_435E4480-A6E0-4187-A521-F9F92B0BF9AD--