Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83104 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11029 invoked from network); 18 Feb 2015 18:41:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Feb 2015 18:41:05 -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:52224] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C1/04-25021-FBCD4E45 for ; Wed, 18 Feb 2015 13:41:04 -0500 Received: (qmail 22474 invoked by uid 89); 18 Feb 2015 18:41:00 -0000 Received: by simscan 1.3.1 ppid: 22468, pid: 22471, t: 0.0694s 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; 18 Feb 2015 18:41:00 -0000 Message-ID: <54E4DCBC.3060002@lsces.co.uk> Date: Wed, 18 Feb 2015 18:41:00 +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: <54E3E27B.2010903@lerdorf.com> <2f99c47df51fa6c73131032ec50fade0@mail.gmail.com> <005201d04b6c$1122d130$33687390$@tutteli.ch> <030f01d04b7f$0c71d1a0$255574e0$@php.net> <034e01d04b9b$2d7c0160$88740420$@php.net> <54E4D0D0.10404@lerdorf.com> <7766B1DB-439B-4AEB-9CF0-1D2C5E7937D1@zend.com> In-Reply-To: <7766B1DB-439B-4AEB-9CF0-1D2C5E7937D1@zend.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Scalar Type Hints v0.4 From: lester@lsces.co.uk (Lester Caine) On 18/02/15 17:55, Zeev Suraski wrote: > We can limit ourselves to values below that limit. If you deal with values above it, be explicit about casting. This is exactly my problem ... Databases are using 64bit primary keys more and more, and having to worry about going over some limit is the very thing that any 'hinting' should be taking care of! This is the very area where using 32bit builds at least provides a level of protection currently. -- 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