Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83926 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 83175 invoked from network); 26 Feb 2015 20:37:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Feb 2015 20:37:24 -0000 Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.223.180 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.223.180 mail-ie0-f180.google.com Received: from [209.85.223.180] ([209.85.223.180:36521] helo=mail-ie0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9A/00-32582-3048FE45 for ; Thu, 26 Feb 2015 15:37:24 -0500 Received: by ierx19 with SMTP id x19so20874651ier.3 for ; Thu, 26 Feb 2015 12:37:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type; bh=IK5DHvLt0Lk9phnqpEPrByEYPgOwY4OFPtOy/DFQx0o=; b=YJ7fq9H0o8HwA7+whJECv3T72gobgGtc++GOedjXa1ueV4r/HNNCoUTDFz2osvUg0P MCcwJ0ViIzQiWvdJxQREXSOIaMDhOA+bVT6xyScBjEo1KpZtQ6u/PNYb3KoRFihlb4Rr tjh6EBMIefW8c7Rrl9pDY9lQja8MQjsBGAtzaljB24pofsE8r/Bar/sfU/PqZTJ7/2hq W35HYWKvWJDK+528ZOlh8i7rwNXPBrCkc+r16VDGrSKFjvbDM/0roeG7JtEsqOHWaj0O 0vi+8Trnp+l+mvKWuTNsngy9qj6STmVQ4BnuPycgNc5mKtOmFbyS73VI+tqM8L4DYF7/ ldTg== X-Gm-Message-State: ALoCoQlVaH9WpRPUeKfkO1EJ6m+ViEEx6fOST+Z7AVoEDqBYA0KzGNh+T6rkw9IycCSKTX8uu74yrWr5HTqFC3KzS9LhwSpK7v2ANf3dEWkVIBKC64dR7FELhcgoo0VW8BtVfcFNCFR3U64EnFKXv+N8nFsPjGL0Tw== X-Received: by 10.43.67.3 with SMTP id xs3mr11693469icb.39.1424983040825; Thu, 26 Feb 2015 12:37:20 -0800 (PST) References: <3d639901ae85227b219e7ee59b3140fe@mail.gmail.com> <42bc7c079a67fe1aa982b5c55ecc2f16@mail.gmail.com> In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGwbbdURx2shUG2o7Zj2Ywptu8MnAHNhHseASj3TG8CBU/YnAHY8IsNAn8zUX0BDEv+qAJWJD9/AgdVbcOczTw0cA== Date: Thu, 26 Feb 2015 22:37:20 +0200 Message-ID: <452b694a394f89662fb1fc7f479be618@mail.gmail.com> To: Anthony Ferrara Cc: internals@lists.php.net Content-Type: text/plain; charset=UTF-8 Subject: RE: [PHP-DEV] A different user perspective on scalar type declarations From: zeev@zend.com (Zeev Suraski) > -----Original Message----- > From: Anthony Ferrara [mailto:ircmaxell@gmail.com] > Sent: Thursday, February 26, 2015 10:24 PM > To: Zeev Suraski > Cc: internals@lists.php.net > Subject: Re: [PHP-DEV] A different user perspective on scalar type > declarations > > Zeev, > > > > When I say you need to worry about them a lot less - I mean that you > > can get 90%+ of the benefits of strict mode, for ALL of your code, > > with a tiny fraction of the hassle. > > From past posts, it's very clear you believe that large projects would > > gradually migrate to being strict across the board. If we compared > > the > > Well then, you've heard things I've never said. I'm referring to this: > A few hundred LOC script would likely never enable strict mode, and would > be just fine because of it (you can mentally keep a few hundred LOC in > your head at one time). > > The larger the project, the more the contributors, the more the benefits > to using strict mode. That's not to say that large projects would > immediately go full strict. It's just pointing out that the tradeoffs > would need to be weighed by the authors. The way I read it, "not immediately going full strict" implied they'd gradually go full strict, as opposed to not at all (in which case saying "That's not to say that large projects will necessarily want to go full strict " would have perhaps been more appropriate). Apologies if I misunderstood you. > > Given that I actually ran Magento, Drupal, WordPress and both the > > Symfony and ZF2 skeleton apps with the new coercive ruleset, and I > > already know there's no reason at all to be scared. More on that > > later today or early tomorrow - running more tests. > > They run without triggering E_DEPRECATED errors? Because that means they > will break with 8 (which by your own words is closer to 2-3 years out than > 9- > 10). Not without, but at least in my testing so far - the things that are picked up by the coercive rule-set are quite precise and have excellent signal to noise ratio. We're still working on the patch so I don't want to provide the results just yet because they might be bogus, but I'll share them as soon as they're stable. Thanks, Zeev