Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79839
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.49 as permitted sender)
Message-ID: <5496571E.5070404@gmail.com>
Date: Sat, 20 Dec 2014 21:14:06 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Yasuo Ohgaki <yohgaki@ohgaki.net>, nf.laupretre@yahoo.fr
CC: "internals@lists.php.net" <internals@lists.php.net>
References: <000c01d01ca0$7e70c850$7b5258f0$@yahoo.fr> <CAGa2bXbWM+pJNWkzyy=8vtVvAhQ5Hv4BgLr2cRkvq0iFGdV9rA@mail.gmail.com>
In-Reply-To: <CAGa2bXbWM+pJNWkzyy=8vtVvAhQ5Hv4BgLr2cRkvq0iFGdV9rA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Proposal for PHP 7 : case-sensitive symbols
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> is not recommended at all. Keeping not recommended spec forever is not
> a good idea. IMHO. Using strtolower() all over place in the Engine to keep

There's a huge difference between "not recommended" and breaking the
code. Using if() without braces, or inconsistent indentation - is not
recommended. Making such code not work would be a huge mistake.

> It's BC, but it would be easy spot it by an compatibility check script. Once
> case is used properly, scripts run both new and old PHP. Therefore,
> BC issue is not critical.

There's no "therefore" - you'll still have to fix all that code, and if
you think it all will be findable by a simple script, you severely
underestimate the dynamic nature of things people do with PHP. This is a
very big change and should not be dismissed lightly.

-- 
Stas Malyshev
smalyshev@gmail.com