Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78040 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47447 invoked from network); 14 Oct 2014 17:48:41 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Oct 2014 17:48:41 -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:55863] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 52/4D-18603-7F16D345 for ; Tue, 14 Oct 2014 13:48:40 -0400 Received: (qmail 29259 invoked by uid 89); 14 Oct 2014 17:48:36 -0000 Received: by simscan 1.3.1 ppid: 29253, pid: 29256, t: 0.0596s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 14 Oct 2014 17:48:35 -0000 Message-ID: <543D61F3.3000000@lsces.co.uk> Date: Tue, 14 Oct 2014 18:48:35 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: internals@lists.php.net References: <8C47FA53-0964-49C0-963C-332A936348A5@ajf.me> <543CE41B.5020308@sugarcrm.com> <543D5C78.9040905@sugarcrm.com> In-Reply-To: <543D5C78.9040905@sugarcrm.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Big Integer Support From: lester@lsces.co.uk (Lester Caine) On 14/10/14 18:25, Stas Malyshev wrote: > I don't see why you'd have two code paths. If you need bigints and they > are not there, then you just fail, like with any extension your code > needs and is not installed. If it's there, you just continue working. > All the code existing now doesn't need bigints, and even in the future > most code won't need it. But for some code it would just work like > before, only with unlimited range now. 'bitinteger!' I'm still waiting to see how we handle 'BIGINT' under this rfc since that is something every database driver does need to handle. -- 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