Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79071 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 86165 invoked from network); 21 Nov 2014 09:57:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Nov 2014 09:57:20 -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:51516] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 99/28-32541-E7C0F645 for ; Fri, 21 Nov 2014 04:57:19 -0500 Received: (qmail 32137 invoked by uid 89); 21 Nov 2014 09:57:15 -0000 Received: by simscan 1.3.1 ppid: 32126, pid: 32130, t: 0.0604s 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.177.82.94) by mail4.serversure.net with ESMTPA; 21 Nov 2014 09:57:15 -0000 Message-ID: <546F0C7B.3060900@lsces.co.uk> Date: Fri, 21 Nov 2014 09:57:15 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: internals@lists.php.net References: <3A69F0F5-C5FE-415D-A894-193D9F146854@gmail.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [VOTE][RFC] Safe Casting Functions From: lester@lsces.co.uk (Lester Caine) On 21/11/14 02:10, Yasuo Ohgaki wrote: > To be honest, I have mixed feeling for this FRC. > Stricter type check is good. However, it requires runtime cost. One of the area where it is being held up as good practice is filtering data which is then passed to a database. With best practice on handling THAT process, the database will be validating data being passed to an integer or float field as well, and may not follow the same 'new' rules. There are a number of areas where this is just bloat which has to be handled differently anyway. For PHP7 the whole picture needs to be reviewed, not just yet more sticking plasters. -- 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