Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101759
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.47 as permitted sender)
To: Wes <netmo.php@gmail.com>, PHP Internals <internals@lists.php.net>
References: <CAOv67gvh_TM8B+ZvJeMwQDN7wnC+n7JiW78Ydk+V3wRjsXigBA@mail.gmail.com>
Message-ID: <f57d69c2-e477-3f41-75f5-92c5eee9a998@gmail.com>
Date: Sun, 4 Feb 2018 01:07:25 -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: <CAOv67gvh_TM8B+ZvJeMwQDN7wnC+n7JiW78Ydk+V3wRjsXigBA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Deprecation of fallback to root scope
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> I hope you like it. Let me know what you think.
> 
> https://wiki.php.net/rfc/fallback-to-root-scope-deprecation

I do not see how this makes sense. This RFC claims there's no BC
breakage, while it deprecates one of the most widely used functions of
the language (using unqualified global functions from inside namespaces)
and adds warnings which will break a lot of existing code (and yes,
notice and warning are basically the same).

I do not see how it makes sense to force people to use \strlen
everywhere (since most of the code in large apps uses namespaces now)
for a tiny and rare possibility that someone would override strlen.
Unless I serously misunderstand what this RFC is proposing, I am
absolutely against it and think doing something like this would be
harmful to PHP. Am I missing something here?
-- 
Stas Malyshev
smalyshev@gmail.com