Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74392 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 29816 invoked from network); 20 May 2014 22:36:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 May 2014 22:36:27 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.47 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.47 mail-la0-f47.google.com Received: from [209.85.215.47] ([209.85.215.47:54901] helo=mail-la0-f47.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 74/D0-24198-9E8DB735 for ; Tue, 20 May 2014 18:36:26 -0400 Received: by mail-la0-f47.google.com with SMTP id pn19so947739lab.20 for ; Tue, 20 May 2014 15:36:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=qi5JWIFIPJR8ndhzPWmZ15CBtDNptGUI+pqu5WenojA=; b=sSi5ZW0X7C8oBrVjtHwHlqiRLa/VmgPvV1CQuEGyFcHs1dXpsWqj4rLzbfE4QjGDd+ XzsoPVNbqM9mz3FVUdl1x7AB4HEPcdAQU2zZCrlH1I/z2489JKJHc3qzrsAyugQUxRr1 VsK1ZYsdVgB1Ctum3LTH6OfyYr/wNdUR4sZ//W6ZAAX0pucXyk1B4RN+GFWFRnRAJ9sC ursvpC4QU5qp1FGSKZR4jXiiilHeDX2HMfWJTX+jI2DAtjmRDfdJBYt25r2Ks79JhOWN 1mYMoiDhI+dZH9rQ8lOscV0lGvKkMHvwRpfOBp3y2c4cW6/5QXahIQ6OwyhPxnO6rcPN JZKA== X-Received: by 10.152.26.99 with SMTP id k3mr4127250lag.68.1400625383102; Tue, 20 May 2014 15:36:23 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.205.73 with HTTP; Tue, 20 May 2014 15:35:42 -0700 (PDT) In-Reply-To: <537BC669.2030704@sugarcrm.com> References: <537BC669.2030704@sugarcrm.com> Date: Wed, 21 May 2014 07:35:42 +0900 X-Google-Sender-Auth: LrC92FV6i_OZIgOzVATgk1zP3Ls Message-ID: To: Stas Malyshev Cc: Nikita Popov , Arvids Godjuks , PHP internals Content-Type: multipart/alternative; boundary=089e0160be4e6c5df804f9dc8261 Subject: Re: [PHP-DEV] Re: 64bit and phpng, votes and plans From: yohgaki@ohgaki.net (Yasuo Ohgaki) --089e0160be4e6c5df804f9dc8261 Content-Type: text/plain; charset=UTF-8 Hi Stas, On Wed, May 21, 2014 at 6:17 AM, Stas Malyshev wrote: > > 64bit int if int is 64bit. I prefer consistency, so array int key is > better > > to support > > 64bit int key. IMHO. > > Given that 99.9999% of PHP users will never need it, but 100% of PHP > users will pay in performance for each size increase, we need to be > careful here. "Consistency" is not more magic word than "security". > > > Similar argument applies to string also. It would be WTF, when users try > to > > access string offset over 32bit values. Data dealt with PHP is getting > > larger > > and larger. It would be an issue sooner or later. > > Not likely, unless somehow PHP becomes language of choice for processing > big data. Which I don't see exactly happening. But if it ever happens, > we can deal with it then. I think many people don't like PHP and/or switching to other languages are concerned about consistency as language. Users will just switch tool, so these would be issues. We just loose users(I mean we loose developers). I'm really concerned about performance as much as security/consistency like you. However, average web developers are not. Most developers prefer large and slow web app frameworks. This is the reality. I think we must face our users(developers). Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --089e0160be4e6c5df804f9dc8261--