Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105135
MIME-Version: 1.0
References: <CA+kxMuQb1B1eQaXw1fDJjUE_RecTh9TaMFpb1-MkkVM-mmfrYA@mail.gmail.com>
 <D8BB6AA5-CAEB-446E-BC9B-81C124CC5898@cschneid.com> <CAPKYkKxa7VdL04qBWhs=_MPUm-ZJaRVkoUqP978A2dv96i6iSg@mail.gmail.com>
 <CAPhkiZxh+kwb6h_0y27c1dxiPNBH6DCOTATFHmZhT_EFLb0-7A@mail.gmail.com> <00b701d4ed5c$27f77550$77e65ff0$@jhdxr.com>
In-Reply-To: <00b701d4ed5c$27f77550$77e65ff0$@jhdxr.com>
Date: Mon, 8 Apr 2019 03:18:16 +0100
Message-ID: <CA+kxMuQUDtojsRuVdJ8u6TsXJ1Qjqm87EugDXQi_ZMgAAahHNQ@mail.gmail.com>
To: CHU Zhaowei <me@jhdxr.com>
Cc: Andrey Andreev <narf@devilix.net>, Chase Peeler <chasepeeler@gmail.com>, 
	Christian Schneider <cschneid@cschneid.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] bool values and increment operators?
From: Danack@basereality.com (Dan Ackroyd)

On Sun, 7 Apr 2019 at 17:08, CHU Zhaowei <me@jhdxr.com> wrote:
>
> It there anyone working on this?

I'm planning to. I've just been also thinking about arrays and nulls
with pre/post inc/decrement.

I'm guessing code that is 'intentionally' doing:

$foo = false;
$foo++;

and

$foo = [];
$foo++;

are going to be relatively rare, and so would be small BCs.

Whereas code that is doing:

$foo = null;
$foo++;

e.g. through something like:

error_reporting(0);
$bar = [];
$foo = $bar['bad_key'];
$foo++;

Are going to be more common, and so would be a large BC break.

Though seeing as since PHP 7.0 we have the null coalesce operater,
that code can be re-written to have an explicit default, and not emit
an error as:

$bar = [];
$foo = $bar['bad_key'] ?? 0;
$foo ++;

> In addition, I'm thinking whether it's possible and necessary to add a global
> strict mode (like "use strict" in js) in PHP 8 to deal with this kind of unexpected
> surprise. I know we have declare(strict_types=1) but it only works for functions
> and it's limited to call from current file.

A global mode wouldn't be good - it would have the same problem as ini
settings have; libraries that are written needing one mode, can't be
sure they would be used in that mode.

An alternative idea of having settings per namespace has been
mentioned before with the config settings per library managed through
something at the package manager layer, e.g. Composer.

cheers
Dan
Ack