Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81924 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87694 invoked from network); 5 Feb 2015 13:40:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Feb 2015 13:40:43 -0000 Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.177 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.177 mail-we0-f177.google.com Received: from [74.125.82.177] ([74.125.82.177:37294] helo=mail-we0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A3/0C-27691-AD273D45 for ; Thu, 05 Feb 2015 08:40:42 -0500 Received: by mail-we0-f177.google.com with SMTP id l61so7699437wev.8 for ; Thu, 05 Feb 2015 05:40:39 -0800 (PST) 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=TY0mrL4cdelkBlD+Pts/wvVqCfDELS2/wiMRZGzCUJ0=; b=UHxl/hnWDF/rsR3SO+YtoPn63CTe0DOmbMaPc1hM1VVwNY35hrfg+fl9hX7U9dOl4e 13hJr8PnQFbD31PgoZNkL+ccGZjxKSUsjsMDupTvkbCAT9tvI8YTKQmhmpR9wM8y45FR AF5jdbgYRZEedF6wFH3/cec3L1gSOrDsgfMeem4a19YVMPu1LL3WDcD30Nssg1C2rIoI b7g9SZebXNBjbI7x5eEukCaPFN84j0IwzobCs5o65CYY3nD7EijV//6CDAnLB3p57YEY vj1DVTyODJgUnYIcHh5g+vrjMBOVdX/zDDpdHHW7j8l0aO7ofKwNr+ZpC+66D/Lsm9zO iBCw== X-Received: by 10.180.72.241 with SMTP id g17mr15555094wiv.58.1423143638734; Thu, 05 Feb 2015 05:40:38 -0800 (PST) Received: from [192.168.0.172] ([62.189.198.114]) by mx.google.com with ESMTPSA id n6sm7460282wjy.8.2015.02.05.05.40.37 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Feb 2015 05:40:37 -0800 (PST) Message-ID: <54D372CD.5070007@gmail.com> Date: Thu, 05 Feb 2015 13:40:29 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: internals@lists.php.net References: <54D34CD6.6020401@lsces.co.uk> <585A6531-BFF1-4B40-9052-518518A9409F@ajf.me> <54D36322.8080805@lsces.co.uk> In-Reply-To: <54D36322.8080805@lsces.co.uk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] hints and constraints From: rowan.collins@gmail.com (Rowan Collins) Lester Caine wrote on 05/02/2015 12:33: > On 05/02/15 11:37, Andrea Faulds wrote: >> The current description isn’t totally inaccurate, but I had considered renaming the RFC since “big integer support” implies we don’t already have support for big integers, though we do in the form of ext/gmp. A better title for the RFC might be “make PHP integer type be arbitrary-precision”. Still, it’s a minor issue at best. > Current integer variable has a constrained value. 64bit 'fixes' have > created a new set of rules to go with that. There is nothing new about PHP's userland int type being 64-bit on 64-bit platforms. For instance, raising 2 to the power of 62 returns exactly the same thing on every version of PHP back to 4.3.0: http://3v4l.org/VBMbv >> That code is also broken on 64-bit platforms, and has been for a decade. Actually, longer: x86 wasn’t the first architecture to support 64-bit, but it supporting it certainly increased the prominence of 64-bit computing. > Broken in a way that was managable, but it is only in the last few years > that windows itself has become 64bit although 32bit builds are still > required in a number of marketplaces since 64bit ones don't work. > That the transition has not been handled well applies everywhere! The classic use of PHP is the LAMP stack: Linux, Apache, MySQL, PHP. Linux distributions have had good support for 64-bit architectures for years, so many, probably most, production installations of PHP are 64-bit builds.