Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96464
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.53 as permitted sender)
MIME-Version: 1.0
Date: Wed, 19 Oct 2016 01:54:02 -0400
Message-ID: <CAEUnE0frtquR63zPwaazcT-k-UCC7uHHZv4xa3zxWAso-GNpjA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=94eb2c092d68af07d6053f316f43
Subject: [PHP DEV] Bugs, BC, Strict Mode??
From: tendoaki@gmail.com (Michael Morris)

--94eb2c092d68af07d6053f316f43
Content-Type: text/plain; charset=UTF-8

I've seen a couple bug fixes come up that create BC breaks for the code
reliant on the broken behavior.

JavaScript has a opt in strict mode for this. Perhaps PHP could do the
same. An opt in mode with the declare directive that turns on bug fixes
that are BC problems.

One recent example, the behavior of parse_url.

The ternary operator being backwards (right to left instead of left to
right as in all other languages) is another.

This approach lets some PHP 8 code be developed early by making troublesome
bug fixes available early.

The drawback is code bloat - both implementations would be in the code at
the same time. Also, core functions would need to check if the calling code
wants the normal or strict version of the function.

Or maybe namespaces and the use (use Strict; ) could handle this.

--94eb2c092d68af07d6053f316f43--