Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83452
Return-Path: <francois@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 34768 invoked from network); 22 Feb 2015 00:28:56 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 22 Feb 2015 00:28:56 -0000
Authentication-Results: pb1.pair.com smtp.mail=francois@php.net; spf=unknown; sender-id=unknown
Authentication-Results: pb1.pair.com header.from=francois@php.net; sender-id=unknown
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.27.42.2 as permitted sender)
X-PHP-List-Original-Sender: francois@php.net
X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr  
Received: from [212.27.42.2] ([212.27.42.2:21066] helo=smtp2-g21.free.fr)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id A1/CC-08895-7C229E45 for <internals@lists.php.net>; Sat, 21 Feb 2015 19:28:56 -0500
Received: from moorea (unknown [82.240.16.115])
	by smtp2-g21.free.fr (Postfix) with ESMTP id E417C4B0188;
	Sun, 22 Feb 2015 01:28:45 +0100 (CET)
Reply-To: <francois@php.net>
To: "'Anthony Ferrara'" <ircmaxell@gmail.com>,
	"'Zeev Suraski'" <zeev@zend.com>
Cc: "'PHP internals'" <internals@lists.php.net>
References: <7ef509ef10bb345c792f9d259c7a3fbb@mail.gmail.com>	<CAAyV7nHq_-9jyRcwJmiAxthmEo3u3MDXcyOC09LV2DETABzCoA@mail.gmail.com>	<8250289916f5128b5bc1a114428d374e@mail.gmail.com>	<CAAyV7nHAicJCQU87YkhZ700a=k4MRqVJtMV-mG4F0MQsn82OfQ@mail.gmail.com>	<e7bfa71fe190a2577b329092b46da5dd@mail.gmail.com>	<CAAyV7nGrh30VdYbU6j3oHwQHX_S81LdQ8iZAe4zZcAT1xOZ-uA@mail.gmail.com>	<b72cac641e4bfddc212c01ae46a40ac5@mail.gmail.com> <CAAyV7nG6uwV7KdbANUveLhczQDk6=yF6df4PcyypxmOJviBx=Q@mail.gmail.com>
In-Reply-To: <CAAyV7nG6uwV7KdbANUveLhczQDk6=yF6df4PcyypxmOJviBx=Q@mail.gmail.com>
Date: Sun, 22 Feb 2015 01:28:52 +0100
Message-ID: <066e01d04e36$88f39650$9adac2f0$@php.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKcPg+jpyYspJS11b5G1A7RBHpKTgFW66vOANg4ZZIBOJUt6QIcwpl/AeIBZpMDDZr3vwJLslGUmv3uYvA=
Content-Language: fr
X-Antivirus: avast! (VPS 150221-0, 21/02/2015), Outbound message
X-Antivirus-Status: Clean
Subject: RE: [PHP-DEV] Coercive Scalar Type Hints RFC
From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=)

> 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.

Regards

Fran=C3=A7ois