Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107003
MIME-Version: 1.0
References: <076701d56978$86020910$92061b30$@php.net> <CADyq6sK4HektgfDpCCFR3=bumyPaf9vn=-WdvaboHybBQKd53g@mail.gmail.com>
 <078e01d5697c$5512bc10$ff383430$@php.net> <CAKws9z1EBSqCFy2wD3cEV49KDSJOd6tT04PrCkxG8+3Hb6WpTA@mail.gmail.com>
 <CAPKYkKw1EU3Qp6W7b19r4kMKPD1HntH+7NQSxSiDNcLXqPERMA@mail.gmail.com>
 <CAKuGYLRWF9jnS-Zs+uRFNN1pgRSvHFpW-FChgNq9Rk282AFFGA@mail.gmail.com>
 <CAPKYkKxUyeWWZY5OyDLtAYiDUYLkwyMjuc_Wq2Y++3C9CP6G1w@mail.gmail.com>
 <CAKuGYLSub6oC=weSbjaPowhKtc3EimmFL6Tm+=D7wm7GeRLP=A@mail.gmail.com>
 <CAPKYkKz7waMPZReyigUmCWWXjMZpHh+K0MWEfQk2UJapmE_VxQ@mail.gmail.com>
 <262D6749-66C3-4544-9FA0-32CDA6EC402A@koalephant.com> <CAPKYkKz64PPBYLpn9dN=rE2x1ecbO04acQQdak6YdiwOipTQQA@mail.gmail.com>
In-Reply-To: <CAPKYkKz64PPBYLpn9dN=rE2x1ecbO04acQQdak6YdiwOipTQQA@mail.gmail.com>
Date: Thu, 12 Sep 2019 14:25:09 -0400
Message-ID: <CAKuGYLTvdFQs2DHPsFM+m1f9j2s8upE79Y+FAt7+WOgXgWpxbA@mail.gmail.com>
To: Chase Peeler <chasepeeler@gmail.com>
Cc: Stephen Reay <php-lists@koalephant.com>, Scott Arciszewski <scott@paragonie.com>, 
	Zeev Suraski <zeev@php.net>, Marco Pivetta <ocramius@gmail.com>, 
	PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000c8f65b05925f4234"
Subject: Re: [PHP-DEV] Changing fundamental language behaviors
From: matthewmatthew@gmail.com (Matthew Brown)

--000000000000c8f65b05925f4234
Content-Type: text/plain; charset="UTF-8"

I'm sure that some people wrote code like this, expecting it to always work
in PHP:

if ($some_condition) define("HELLO", 0);
if (HELLO) { var_dump("got here"); }

The equivalent, relying on buggy behaviour, PHP code looks like

if ($some_condition) $hello = 1;
if (!$hello) { var_dump("got here"); }

If preventing undefined constants wasn't a fundamental change to the
language, neither is preventing undefined variables.

>

--000000000000c8f65b05925f4234--