Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74198 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48507 invoked from network); 14 May 2014 17:28:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 May 2014 17:28:20 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.175 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.216.175 mail-qc0-f175.google.com Received: from [209.85.216.175] ([209.85.216.175:58131] helo=mail-qc0-f175.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 81/BC-15285-3B7A3735 for ; Wed, 14 May 2014 13:28:19 -0400 Received: by mail-qc0-f175.google.com with SMTP id w7so3315933qcr.6 for ; Wed, 14 May 2014 10:28:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7IvhxKJIzTlodDrVvv05NEMHCrLTjNLfw2g7MGexDok=; b=jkokLYWydipYWq3FpSgwbngb3EcdMAyKmwpOooEo5DFOmlvgf6vMJTnOq6y0sNYelR Mz5oFv0/KRrevt+llQkGgf7SXrp5rzeRyFKRzR122F54PhgOjnXNcRj77xpFP3JaH1AF 6/kdG5tU7XGKmltiZkHBPTcw65Fy9TvzKk9oyodPNT2crrN9nSC06jEzy8QfOQ5uDuMz 0jsZ9ki0l/XBnGyah9witumvQ5fpOJ6TMvNrjHGaGkKoB3K2806kFblyXsqYUP7ESqdj /aGTqKYNo59F863wFS/scKoGscvcz5w9dIt6q7i/EY7l3Ew3c59ocZOP+dqmXZidXbOf X+Ng== MIME-Version: 1.0 X-Received: by 10.224.24.201 with SMTP id w9mr5578518qab.72.1400088496440; Wed, 14 May 2014 10:28:16 -0700 (PDT) Received: by 10.140.17.77 with HTTP; Wed, 14 May 2014 10:28:16 -0700 (PDT) In-Reply-To: <4D169A0A-0A59-402B-8479-C63E5C212A63@ajf.me> References: <53732673.3080106@lsces.co.uk> <5373A39E.8050302@hristov.com> <4D169A0A-0A59-402B-8479-C63E5C212A63@ajf.me> Date: Wed, 14 May 2014 19:28:16 +0200 Message-ID: To: Andrea Faulds Cc: Andrey Hristov , PHP Internals Content-Type: multipart/alternative; boundary=001a11c2a2607c0ac304f95f81eb Subject: Re: [PHP-DEV] [VOTE] [RFC] 64 bit platform improvements for string length and integer From: tyra3l@gmail.com (Ferenc Kovacs) --001a11c2a2607c0ac304f95f81eb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, May 14, 2014 at 7:13 PM, Andrea Faulds wrote: > > On 14 May 2014, at 18:10, Andrey Hristov wrote: > > > This is purely academical. And the standard library has to support > everything, it's the standard library. PHP is on its own, and if an > addition is of little use to the most of the developers/scripts, why the > heck it should be in/the default. > > A good solution is to typedef a php_size_t, leave it to uint32_t and fo= r > those, who need more than 4GB in strings and elements they can just build > with size_t as definition. Offer the choice, don't force. > > It is not just =E2=80=9Cpurely academic=E2=80=9D. Here, let me quote Pier= re (in 'Re: > [PHP-DEV] [VOTE] [RFC] 64 bit platform improvements for string length and > integer=E2=80=99, just now) quoting Anthony: > I'm fairly sure than anybody reading this thread will also read the other, so there is no reason to copypaste the mail. If you think it is important, you can quote the relevant parts, or link to the mail if you want to refer the whole thing. Other than that, I'm not sure that you understood what Andrey wrote, his idea would allow to use the size_t types, but it would be a build-time opt-in feature. Personally I don't like the idea, as we would have to support both types, and as this also effects the userland (max length of strings, integer size on windows, etc.) it would be a heavy debugging/maintenance burden. --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --001a11c2a2607c0ac304f95f81eb--