Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83218 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 78691 invoked from network); 19 Feb 2015 16:21:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Feb 2015 16:21:26 -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:39830] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6C/F1-18870-38D06E45 for ; Thu, 19 Feb 2015 11:21:25 -0500 Received: (qmail 25672 invoked by uid 89); 19 Feb 2015 16:21:21 -0000 Received: by simscan 1.3.1 ppid: 25661, pid: 25669, t: 0.0785s 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; 19 Feb 2015 16:21:21 -0000 Message-ID: <54E60D80.8010507@lsces.co.uk> Date: Thu, 19 Feb 2015 16:21:20 +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: <011801d04a07$83ab1c00$8b015400$@php.net> <016f01d04a3a$e9183220$bb489660$@php.net> <022801d04ab1$4a0c47d0$de24d770$@php.net> <1913e09d7f52541901d8574d2080a63f@mail.gmail.com> <7a5d96b34b98ec1f3ee17be7fa6a1e81@mail.gmail.com> <2CBDEB67-3DE3-437D-9AF3-0E6A92027244@zend.com> <4cc0c81c7199a452534bb8edcdb19914@mail.gmail.com> <54E589F6.9030002@garfieldtech.com> <54E5B9DD.6080607@lsces.co.uk> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Reviving scalar type hints From: lester@lsces.co.uk (Lester Caine) On 19/02/15 12:52, Zeev Suraski wrote: >> Now that all made sense! >> > >> > My only grey area is 'allowing sensible ones' where the size is an >> > integral part >> > of what is 'sensible' ... the one where conventional strict typing uses a >> > type >> > of the right size? > I think the guiding principal for these conversions should be no data loss. > This may mean we have different limits on different architectures, depending > on whether they're 32-bit or 64-bit. This still leaves the 'black hole' caused by the fact that databases are actively using 'BIGINT' even on 32 bit platforms. It may be that the only practical approach is gmp, but using that and writing code that selects that on a 32bit platform, then switching to clean 64bit maths on a 64bit platform does not sound like simplifying things? As with other debates, some say ignore 32 bit, and others say lets loose the constraints altogether, but having a fundamental type behave differently depending on platform is a problem? -- 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