Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98027
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <0c5fc86b-5050-fe73-7afa-b3e5a38ad370@gmail.com>
References: <0c5fc86b-5050-fe73-7afa-b3e5a38ad370@gmail.com>
Date: Sun, 29 Jan 2017 21:50:52 +0100
Message-ID: <CAF+90c_TNkpSu=3mgjDaYg6YZb5YUCVEtehdRF=4-=ZWr0tRgQ@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f403045e61fcd271f6054741dad8
Subject: Re: [PHP-DEV] [RFC] Deprecate and Remove Bareword (Unquoted) Strings
From: nikita.ppv@gmail.com (Nikita Popov)

--f403045e61fcd271f6054741dad8
Content-Type: text/plain; charset=UTF-8

On Sun, Jan 29, 2017 at 8:33 PM, Rowan Collins <rowan.collins@gmail.com>
wrote:

> Good evening all!
>
> 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.
>

Fully agree with this proposal.

Also agree with the choice of throwing a Warning instead of a Deprecation.
Throwing a Deprecation would essentially *downgrade* the current error
level, which does not appear to be prudent.

Nikita

--f403045e61fcd271f6054741dad8--