Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101790
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.53 as permitted sender)
To: "Christoph M. Becker" <cmbecker69@gmx.de>,
 Benjamin Eberlei <kontakt@beberlei.de>, Wes <netmo.php@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
References: <CAOv67gvh_TM8B+ZvJeMwQDN7wnC+n7JiW78Ydk+V3wRjsXigBA@mail.gmail.com>
 <CAEPJdunk-uWhaqOtUP24qNzqv-EBvJnJncikPsfLBtjPkfwH8g@mail.gmail.com>
 <07d9e3a0-d516-aa77-4818-ce8b02e8dd08@gmail.com>
 <79b192e6-a6bd-bd13-6bd4-b56011a5eac2@gmx.de>
Message-ID: <8772d304-b205-e46c-1383-9f194277dcdb@gmail.com>
Date: Tue, 6 Feb 2018 11:31:37 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:58.0)
 Gecko/20100101 Thunderbird/58.0
MIME-Version: 1.0
In-Reply-To: <79b192e6-a6bd-bd13-6bd4-b56011a5eac2@gmx.de>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Deprecation of fallback to root scope
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

>>> To get the same benefits (jit and such) wouldn't it be better to introduce
>>> a "use function root;" or similar statement or a declare() to specify this
>>> file imports all root functions?
>>
>> We already have this right now, […]
> 
> Do we?  AFAIK, it is not possible to import *all* functions (or even all
> symbols, for that matter) of a namespace, without explicitly mentioning
> them.

We are talking about global namespace aka standard PHP functions, so it
works out of the box. If you're talking about non-global namespace,
there's no such thing as "all functions of a namespace" at all, and even
if there were, in most cases it's the wrong thing (excepting some rare
cases like you want to override all PHP function for testing, etc.) to
do. Namespaces are meant to keep things separate, so blanket imports
just put us back into a pre-namespace world with all the problems that
existed there.
Granted, there are rare cases - as overriding whole extension or whole
standard library - but they are rare. In overwhelming majority of cases,
this is not what should be done and if you do it, you usually get in
trouble.
-- 
Stas Malyshev
smalyshev@gmail.com