Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105134
To: internals@lists.php.net
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>
Message-ID: <aff4a5ec-b0a1-d872-f94a-b80406c16a50@gmail.com>
Date: Sun, 7 Apr 2019 18:15:51 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <00b701d4ed5c$27f77550$77e65ff0$@jhdxr.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] bool values and increment operators?
From: rowan.collins@gmail.com (Rowan Collins)

On 07/04/2019 17:08, CHU Zhaowei wrote:
> 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.


I'm not a fan of a generic "strict mode" the way JS has it, because it 
only works once: if you add more behaviours later, the BC break is just 
as bad as if the switch wasn't there. I wonder if in 10 years time, 
someone will propose a "use stricter" mode.

Perl's "pragma" system is more flexible, and notably works at the file 
or block level, like PHP's declare statements. The most common pragmas 
are "strict", "warnings", and "feature", each of which has a set of 
sub-categories which can be individually enabled and disabled. You can 
also opt into all features as of a particular version (and require that 
version), again within a single lexical scope. The downside is that this 
leads to a lot of different combinations, in keeping with the Perl motto 
of There More Than One Way To Do It.

The big downside of all this is that even if the compiler understands 
what all the combinations of flags will do, the human reading the code 
won't necessarily, so having declare(increment_warnings=1) probably 
doesn't add much over just documenting the change somewhere.

Regards,

-- 
Rowan Collins
[IMSoP]