Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98029
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.20 as permitted sender)
To: Rowan Collins <rowan.collins@gmail.com>,
 PHP Internals <internals@lists.php.net>
References: <0c5fc86b-5050-fe73-7afa-b3e5a38ad370@gmail.com>
Message-ID: <68b674b4-c6e2-b663-6d78-e32c52857a11@gmx.de>
Date: Mon, 30 Jan 2017 00:03:44 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <0c5fc86b-5050-fe73-7afa-b3e5a38ad370@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [RFC] Deprecate and Remove Bareword (Unquoted) Strings
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 29.01.2017 at 20:33, Rowan Collins wrote:
> Currently, if the constant FROB_ACTIVE is not defined, the code "echo
> FROB_ACTIVE;" results in an E_NOTICE and the string 'FROB_ACTIVE' being
> displayed. I would like to propose that this be changed to an E_WARNING
> in PHP 7.2, and to an Error in PHP 8.0.
> 
> My reasoning for this includes:
> 
> - consistency with other "undefined" errors, including the otherwise
> identical "echo \FROB_ACTIVE;"
> - the fallback to string appears to be largely undocumented except to
> discourage its use
> - the error can mask serious bugs, such as when mis-typing keywords
> 
> I have tried to anticipate some of the questions that will be raised, so
> have drafted an RFC rather than trying to fit all the detail into one
> e-mail: https://wiki.php.net/rfc/deprecate-bareword-strings
> 
> Please read my proposal, and let me know your thoughts. I have placed
> the RFC "under discussion", but will be happy to modify it based on
> feedback, and am in no haste to put it to a vote.

Thanks for bringing this forward, Rowan!

I'm +1 on the proposal by all accounts.

-- 
Christoph M. Becker