Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83732 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 17605 invoked from network); 25 Feb 2015 01:20:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Feb 2015 01:20:22 -0000 Authentication-Results: pb1.pair.com header.from=francois@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=francois@php.net; spf=unknown; 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:40505] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 25/E1-24698-5532DE45 for ; Tue, 24 Feb 2015 20:20:21 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id 7B2CB4B017C; Wed, 25 Feb 2015 02:20:02 +0100 (CET) Reply-To: To: "'Pierre Joye'" Cc: "'Yasuo Ohgaki'" , "'Zeev Suraski'" , "'Anthony Ferrara'" , "'PHP internals'" References: <081001d04fe8$dcbc0160$96340420$@php.net> <081901d04fee$e6de8d60$b49ba820$@php.net> <086901d05035$22055d10$66101730$@php.net> In-Reply-To: Date: Wed, 25 Feb 2015 02:20:14 +0100 Message-ID: <08cc01d05099$36107150$a23153f0$@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: AQJ74oXxmOVhQl9Zr86VtmzdwQ7CVQLTGD0bAWVTmDECJvyKPQGhNfNmAUinERKbXx5PAA== Content-Language: fr X-Antivirus: avast! (VPS 150224-1, 24/02/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] Coercive Scalar Type Hints RFC - BC breaks From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) Hi, > De : Pierre Joye [mailto:pierre.php@gmail.com] > > How do you test apps with actual production data? What a given code is > being fed with in production, everywhere, using random > application&users specific data or inputs. I personally have no codebase to test. These results come from a simple = PHP core 'make test, probably not representative of a real application, = I agree. I expected ML members to try the tool on their codebase and return = numbers but, as usual, after everyone asked for a BC break evaluation = tool, now it is here and nobody uses it. I cannot do more than providing the tool. If nobody wants to use it, = we'll have to make a decision based on the few not so representative = numbers we have. But I won't accept arguments on potential *huge* BC = break if none is able to give 10 minutes to evaluate the *real* risk. Regards Fran=C3=A7ois