Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83453 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 37558 invoked from network); 22 Feb 2015 00:52:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Feb 2015 00:52:37 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.54 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.192.54 mail-qg0-f54.google.com Received: from [209.85.192.54] ([209.85.192.54:35765] helo=mail-qg0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 29/3D-08895-45829E45 for ; Sat, 21 Feb 2015 19:52:37 -0500 Received: by mail-qg0-f54.google.com with SMTP id z60so19665771qgd.13 for ; Sat, 21 Feb 2015 16:52:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=r9eHbFy+b+a9QYB0O6Y6IeAmOix4HtWCusxfH3GzDos=; b=IxS0tg2xU/eLRPX9eEqEClLBL9CkZn9sUAM5Q9437d9xoHhCJH1GAZNf4NVzIy6hDo XuaIIDQRL3F8qrVU7fLEjfeJHjIYifbUqsqxqqK+tzIdC/6cFZ1K/uW/9Iwhne/Z0uYH I/ah/p1YtaEZTKBW+xt4r/PIQEsiJ0zZzwJdh4iM1HPhQz+IQrgJiYmlZay0Zc6ERAKN cOdlhP7Tj7Ptx5KNgoKyjABG2tgUhp7BKOiVUCC+MIbqgvSwDv+KIgg3CQWOzAhMgWVr BqOBLQpgxxeGHspVmJcVkEQU3LzbJ1TuxfyvGirA8r64RWaepDbzJMdLFCiYECloKLbs rs4A== MIME-Version: 1.0 X-Received: by 10.140.95.179 with SMTP id i48mr10286944qge.4.1424566354282; Sat, 21 Feb 2015 16:52:34 -0800 (PST) Received: by 10.96.39.195 with HTTP; Sat, 21 Feb 2015 16:52:33 -0800 (PST) Received: by 10.96.39.195 with HTTP; Sat, 21 Feb 2015 16:52:33 -0800 (PST) In-Reply-To: <066e01d04e36$88f39650$9adac2f0$@php.net> References: <7ef509ef10bb345c792f9d259c7a3fbb@mail.gmail.com> <8250289916f5128b5bc1a114428d374e@mail.gmail.com> <066e01d04e36$88f39650$9adac2f0$@php.net> Date: Sat, 21 Feb 2015 16:52:33 -0800 Message-ID: To: francois@php.net Cc: Anthony Ferrara , PHP internals , Zeev Suraski Content-Type: multipart/alternative; boundary=001a11c16dfc8190ab050fa2b39c Subject: RE: [PHP-DEV] Coercive Scalar Type Hints RFC From: pierre.php@gmail.com (Pierre Joye) --001a11c16dfc8190ab050fa2b39c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Feb 21, 2015 4:29 PM, "Fran=C3=A7ois Laupretre" wrote= : > > > De : Anthony Ferrara [mailto:ircmaxell@gmail.com] > > Saying that turning on an optional and previously unavailable option inside > > code causing code breaks is any way a " BC" break is pure FUD. > > Who talked of BC break for this ? > > I probably missed something because there's no BC break here, just an extremely probable disaster scenario. > > If people massively turn strict-type on because they see on twitter/google/fantasm that it is detecting more errors (and history shows it *will* happen), we have a big problem, because can only be massive casting. Nothing exaggerated here and history again shows that 'people know what they're doing' is not serious. > > "Strict types are sexy. I want to use them on my old codebase. It will help me finding bugs". Human. Basic. Don't think that's FUD. Saying that everyone will turn it on in every possible situations or legacy codes is FUD and pure speculation. My gut feeling, having quite a large users base to back my rough estimation, is that most won't even know or notice it. > Regards > > Fran=C3=A7ois > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > --001a11c16dfc8190ab050fa2b39c--