Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83873 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 53002 invoked from network); 26 Feb 2015 08:29:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Feb 2015 08:29:01 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:33985] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E3/C0-47686-A49DEE45 for ; Thu, 26 Feb 2015 03:28:59 -0500 Received: (qmail 13013 invoked by uid 89); 26 Feb 2015 08:28:56 -0000 Received: by simscan 1.3.1 ppid: 13005, pid: 13009, t: 0.0700s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@86.189.147.37) by mail4.serversure.net with ESMTPA; 26 Feb 2015 08:28:56 -0000 Message-ID: <54EED947.8040704@lsces.co.uk> Date: Thu, 26 Feb 2015 08:28:55 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: internals@lists.php.net References: <7ef509ef10bb345c792f9d259c7a3fbb@mail.gmail.com> <8250289916f5128b5bc1a114428d374e@mail.gmail.com> <09da01d05174$cd7382e0$685a88a0$@php.net> <0a0e01d0519b$0c9338a0$25b9a9e0$@php.net> In-Reply-To: <0a0e01d0519b$0c9338a0$25b9a9e0$@php.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Coercive Scalar Type Hints RFC From: lester@lsces.co.uk (Lester Caine) On 26/02/15 08:05, François Laupretre wrote: > You're probably right but I don't understand what you mean with 'casting'. AFAIK, we are not touching casting rules, implicit or explicit. BUT ... While Coercive Type Rules don't actually cast, they fail in different ways to what the cast would have been, so someone who HAS cast the value before calling then fails simply because the rules are different? I have never used things like 100kg, and I don't see an easy way to convert that to perhaps 100000 gms, but it is a basic part of current PHP so ANY dilution of that should be covered properly. Introducing new rules should mirror across all relevant areas, and I find this a big negative to Coercive STH. But Strict STH is equally bad since again it is not equally applied across all code. One 'cherry picks' when to switch on Strict, one changes the rules that don't fit for Coercive. Neither deserve acceptance because both are only creating more divergence. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk