Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71441 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48128 invoked from network); 23 Jan 2014 15:53:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jan 2014 15:53:08 -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.204 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.204 mail4.serversure.net Linux 2.6 Received: from [217.147.176.204] ([217.147.176.204:42368] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AC/41-39789-0EA31E25 for ; Thu, 23 Jan 2014 10:53:06 -0500 Received: (qmail 6456 invoked by uid 89); 23 Jan 2014 15:53:01 -0000 Received: by simscan 1.3.1 ppid: 6446, pid: 6453, t: 0.0616s scanners: attach: 1.3.1 clamav: 0.96/m:52 Received: from unknown (HELO linux-dev4.lsces.org.uk) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 23 Jan 2014 15:53:01 -0000 Message-ID: <52E13B66.4060502@lsces.co.uk> Date: Thu, 23 Jan 2014 15:55:18 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 SeaMonkey/2.23 MIME-Version: 1.0 To: PHP internals References: <52E0F55F.4040802@lsces.co.uk> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] 64 bit platform improvements for string length and integer From: lester@lsces.co.uk (Lester Caine) Martin Keckeis wrote: > If i look on the progress list, the most common used extensions are already ported? > https://wiki.php.net/rfc/string-size_t/progress I'm still trying to clear up just where we are with handling 64bit values being returned for example from SQL queries. Currently these are returned as numeric strings rather than integer for compatibility with 32bit systems. Having been - and on a few legacy sites - still working with 32bit windows, I expect to see the same return from both 32 and 64bit systems, however it would seem that on a few extensions 'bugs have been fixed' where an integer value is not returned as 64 bit. Certainly on the Firebird/Interbase driver I do not expect 'BIGINT' to be returned as an 'integer' on a 32bit system, and it's this distinction that I'm not seeing documented ... for every extension? -- 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