Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98100
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 84.19.169.162 cause and error)
Message-ID: <1485902993.28761.7.camel@kuechenschabe>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Date: Tue, 31 Jan 2017 23:49:53 +0100
In-Reply-To: <1485902801.28761.5.camel@kuechenschabe>
References: <0c5fc86b-5050-fe73-7afa-b3e5a38ad370@gmail.com>
	 <1485902801.28761.5.camel@kuechenschabe>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] Deprecate and Remove Bareword (Unquoted) Strings
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Tue, 2017-01-31 at 23:46 +0100, Johannes Schlüter wrote:
> Hi,
> 
> On Sun, 2017-01-29 at 19:33 +0000, 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.
> 
> related: There is another context where unquoted strings are used:
> 
>    $a = [ "foo" => "bar" ];
>    echo "Let's go and have a drink in a $a[foo]!";

Oh and there's another case:

   foo.php?a[foo]=bar

> Any thoughts about continuing to allow that?

I'm not saying we have to change those. But I believe the symmetry there
is part of the historic reason.

johannes