Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74396 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38509 invoked from network); 21 May 2014 00:05:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 May 2014 00:05:49 -0000 Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.216.180 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.216.180 mail-qc0-f180.google.com Received: from [209.85.216.180] ([209.85.216.180:55960] helo=mail-qc0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F8/42-24198-CDDEB735 for ; Tue, 20 May 2014 20:05:49 -0400 Received: by mail-qc0-f180.google.com with SMTP id i17so2006267qcy.39 for ; Tue, 20 May 2014 17:05:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=I6yE1Vlw/hEazGgU34HzdbkZm8KoOM7bxw7iJDBubQs=; b=l/TQt9T7NhAuqczrEtQSurZRQ0ziSlJOlwXsT293Wf7oGssJcjxhqw8uwO1xpGu4VJ 9Oe8ojb5dpISLEf0/6sJyx6lDidAldeQFkYcSq5xocaj0GqHeYIVkLJtd/WIOfWD6JGM A8klh1p7o8CbqrSbxElV0q7AU02lcUjCDUcYjLcEhHaPt/GjFoyfWgAiijSjYiG80N17 0m6VPe93X2jXYwAAnRfTlqvu5wraUTu6/wGpqltlNKHnhsT0ls/xu7m18LCrw90wtrpL IZaUqoHrcn15WWeGcXo+dxiaEkLIuKYEc64Fosny6kMssolvYKH2OtgX2TnWwCa/IzFR 9kmg== X-Gm-Message-State: ALoCoQlkpZ3Qa8wCfgvsAoEHIFtnbttypuE2Iw5NWhN9p8d5MFhmd1NosWcblqRwm2Adz/ujOwyQ X-Received: by 10.140.23.166 with SMTP id 35mr62056741qgp.89.1400630745573; Tue, 20 May 2014 17:05:45 -0700 (PDT) Received: from [192.168.200.30] (c-50-131-44-225.hsd1.ca.comcast.net. [50.131.44.225]) by mx.google.com with ESMTPSA id r6sm35017560qab.40.2014.05.20.17.05.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 20 May 2014 17:05:44 -0700 (PDT) Message-ID: <537BEDD7.3060808@lerdorf.com> Date: Tue, 20 May 2014 17:05:43 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Lester Caine , internals@lists.php.net References: <537BC669.2030704@sugarcrm.com> <537BDDEF.9070107@lerdorf.com> <537BEBA7.70807@lsces.co.uk> In-Reply-To: <537BEBA7.70807@lsces.co.uk> X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IO5LMtIPa2OJf1jEl5rfoMSF1DOmrVmpw" Subject: Re: [PHP-DEV] Re: 64bit and phpng, votes and plans From: rasmus@lerdorf.com (Rasmus Lerdorf) --IO5LMtIPa2OJf1jEl5rfoMSF1DOmrVmpw Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 5/20/14, 4:56 PM, Lester Caine wrote: > On 20/05/14 23:57, Rasmus Lerdorf wrote: >> So let's not assume that just because one segment of the userbase >> screams the loudest that this segment is representative. We have a lar= ge >> and diverse userbase and we need to make balanced decisions. >=20 > Handling BIGINT variables as a single 64bit number rather than as a > string of characters would seem to be the more productive way of > working, but is incompatible with 32bit platforms? It's working out > exactly which path is the most productive which is the current question= =2E > If a 64bit integer is supported as a native variable, would it be > practical to have it available on a 32bit platform? Having potentially > to have to code for two different scenarios is not the best way of > moving forward? That has absolutely nothing to do with 64-bit string offsets which is what we are discussing here. -Rasmus --IO5LMtIPa2OJf1jEl5rfoMSF1DOmrVmpw Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org iEYEARECAAYFAlN77dcACgkQlxayKTuqOuBCVACbBu/XJgAgDmrkCbu1Df++iPMg 4eEAn31ldlCYntRc4ZUJImfU8PLmRYNC =unXR -----END PGP SIGNATURE----- --IO5LMtIPa2OJf1jEl5rfoMSF1DOmrVmpw--