Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78043 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 53285 invoked from network); 14 Oct 2014 18:03:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Oct 2014 18:03:33 -0000 Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.208 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 192.64.116.208 imap2-3.ox.privateemail.com Received: from [192.64.116.208] ([192.64.116.208:37289] helo=imap2-3.ox.privateemail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2A/8E-18603-5756D345 for ; Tue, 14 Oct 2014 14:03:33 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id AB26E8C0083; Tue, 14 Oct 2014 14:03:30 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap2.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap2.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id zRjUZeFR3mGw; Tue, 14 Oct 2014 14:03:30 -0400 (EDT) Received: from [10.0.110.86] (border-converged.hackerdeen.org [89.104.225.218]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id BEAB08C007B; Tue, 14 Oct 2014 14:03:29 -0400 (EDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) In-Reply-To: <543D61F3.3000000@lsces.co.uk> Date: Tue, 14 Oct 2014 19:03:26 +0100 Cc: internals@lists.php.net Content-Transfer-Encoding: quoted-printable Message-ID: References: <8C47FA53-0964-49C0-963C-332A936348A5@ajf.me> <543CE41B.5020308@sugarcrm.com> <543D5C78.9040905@sugarcrm.com> <543D61F3.3000000@lsces.co.uk> To: Lester Caine X-Mailer: Apple Mail (2.1878.6) Subject: Re: [PHP-DEV] [RFC] Big Integer Support From: ajf@ajf.me (Andrea Faulds) On 14 Oct 2014, at 18:48, Lester Caine wrote: > 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. >=20 > '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. If you mean 64-bit ints, this RFC enables them to work on 32-bit too = with exactly the same semantics. No more float overflow. On a 64-bit = machine, they=92re IS_LONG internally, and on 32-bit machines they=92re = IS_BIGINT, but the user doesn=92t need to worry, they both act the same. Assuming I actually get round to updating the DB drivers. -- Andrea Faulds http://ajf.me/