Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83521 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 13230 invoked from network); 23 Feb 2015 01:14:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Feb 2015 01:14:28 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; 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:46328] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C6/D2-33016-2FE7AE45 for ; Sun, 22 Feb 2015 20:14:26 -0500 Received: (qmail 30140 invoked by uid 89); 23 Feb 2015 01:14:23 -0000 Received: by simscan 1.3.1 ppid: 30132, pid: 30136, t: 0.0716s 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; 23 Feb 2015 01:14:23 -0000 Message-ID: <54EA7EEF.9090808@lsces.co.uk> Date: Mon, 23 Feb 2015 01:14:23 +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: <2e4694f9805ee81ea0b2c79eab06c2d6@mail.gmail.com> <83921f861c3378dfc6ea34b6681f2edd@mail.gmail.com> <26a5bb62bd37a3f610b2a6c10f84d855@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] JIT (was RE: [PHP-DEV] Coercive Scalar Type Hints RFC) From: lester@lsces.co.uk (Lester Caine) On 23/02/15 00:25, Anthony Ferrara wrote: > And as the static analyzer traces back, if it finds possibilities that > don't match (for example, if you assigned it directly from $_POST), > it's able to say that either the original assignment or the function > call is an error. Why would using an integer I've passed in a URL be a 'fault'? All of the data navigation functions pass their state via the URL and one simply protects against hackers by filtering the state to a default value if it does not return the correct integer data. -- 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