Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106194 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 53461 invoked from network); 9 Jul 2019 12:47:03 -0000 Received: from unknown (HELO mail.gna.ch) (62.12.172.119) by pb1.pair.com with SMTP; 9 Jul 2019 12:47:03 -0000 Received: from [10.0.1.55] (77-56-180-37.dclient.hispeed.ch [77.56.180.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by darkcity.gna.ch (Postfix) with ESMTPSA id 1A7F721549; Tue, 9 Jul 2019 12:06:39 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) In-Reply-To: Date: Tue, 9 Jul 2019 12:06:39 +0200 Cc: PHP Internals List Content-Transfer-Encoding: quoted-printable Message-ID: References: To: Marco Pivetta X-Mailer: Apple Mail (2.3445.104.11) Subject: Re: [PHP-DEV] [VOTE] Strict operators directive From: cschneid@cschneid.com (Christian Schneider) Am 09.07.2019 um 11:30 schrieb Marco Pivetta : > I wasn't sure about the full implications of this, but after some = thought, > the worst that can happen is excessive strictness, requiring to drop a > single declaration on top of a file =F0=9F=91=8D When you drop the declaration on top of the file the semantics of your = operators suddenly change, e.g. "42" < "7" changes from true to false and you get subtle bugs. And if you try to read other people's code (or even try to copy/paste = it) then make sure you keep in mind which mode they are programming in. - Chris