Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:77888 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 84151 invoked from network); 12 Oct 2014 01:15:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Oct 2014 01:15:57 -0000 Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.50 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.50 mail-wg0-f50.google.com Received: from [74.125.82.50] ([74.125.82.50:63051] helo=mail-wg0-f50.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A7/45-43359-C46D9345 for ; Sat, 11 Oct 2014 21:15:57 -0400 Received: by mail-wg0-f50.google.com with SMTP id a1so6336002wgh.33 for ; Sat, 11 Oct 2014 18:15:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=n0+ZPAYAlErbdfnAlpNU56d71AH3tzGuyaha2AtjWek=; b=bhEIX9IhXyGPEcsWQDntN5aFWyc8rcUTkaV9WdTXA+osd/KDGtte2UI4p9HjbfcG3l gFK9fdOew/cuYOz6o8HGua7GnCteNv7Qml5g7cQD8FAJZCP5WTyVyrSxzUZz+2EcC6B6 8YaXlcMIg2E6SrD85Z9jyQ8ufTpXDqQhHr3jDYh1r6a+bfconfE8ZiDZ7mQ2OREEgsBm a9TGdZXgTGXHQiYb3OJvmQOw9UPKsLdP3cMuizTNxMWQU4GiYwBTY/uoLnQgFIB0eGah GijjgDo7aEms1awCaI+Jkp/SP29nzvk69nua3r/MKNDO3nd2IfQDMF1uxiDr+af0GEGX dQxg== X-Received: by 10.194.143.69 with SMTP id sc5mr13071743wjb.49.1413076553541; Sat, 11 Oct 2014 18:15:53 -0700 (PDT) Received: from [192.168.0.2] (cpc68956-brig15-2-0-cust215.3-3.cable.virginm.net. [82.6.24.216]) by mx.google.com with ESMTPSA id bo14sm7266144wib.13.2014.10.11.18.15.52 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 11 Oct 2014 18:15:52 -0700 (PDT) Message-ID: <5439D642.10804@gmail.com> Date: Sun, 12 Oct 2014 02:15:46 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: internals@lists.php.net References: <8C47FA53-0964-49C0-963C-332A936348A5@ajf.me> <54385BC4.8030405@lsces.co.uk> <54386E55.20407@lsces.co.uk> <5A30388D-AD64-4C6A-8547-A0C98D834A8A@ajf.me> <5438F4D1.1080206@lsces.co.uk> In-Reply-To: <5438F4D1.1080206@lsces.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Big Integer Support From: rowan.collins@gmail.com (Rowan Collins) On 11/10/2014 10:13, Lester Caine wrote: > BIGINT is the SQL99-compliant 64-bit signed integer type It's a matter of context. In C, and therefore in related discussions (which includes the internals of PHP), integers are referred to as "short" (for 16-bit), "long" (for 32-bit) and "long long" (for 64-bit), but never as "big". SQL is unusual in calling a 32-bit integer "BigInt" rather than some variant of "long" or "32", and since we're not discussing databases here, it's of only marginal relevance. I can see why, having spent more time in SQL than C, you might jump to the wrong meaning of "BigInt", and it might even be worth considering this potential confusion when writing the end-user documentation for this new feature, should it be implemented. But, as others have said, that's really not an issue which should dominate the discussion at this stage. -- Rowan Collins [IMSoP]