Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74388 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 18307 invoked from network); 20 May 2014 21:13:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 May 2014 21:13:11 -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.53 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.53 mail-la0-f53.google.com Received: from [209.85.215.53] ([209.85.215.53:47778] helo=mail-la0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E0/91-08771-565CB735 for ; Tue, 20 May 2014 17:13:10 -0400 Received: by mail-la0-f53.google.com with SMTP id ec20so898610lab.12 for ; Tue, 20 May 2014 14:13:06 -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=VygpaAU976bQCVUZUxiz/WPGpAElzF1ZZdJjgnjjX3w=; b=SBptMRuTT9/GouZrVVESOTCVlnFklkCqLcuqMPQVax4e53Ljo/8V0R39IZTk5LzEuB b/zymuUSWlBdz6BAzpHmaEsQgsft2vXIRf6xTM7/XEjVtnhgcDOrs2RpNk9IVgrqHPf9 lg+QinOfkzXPQoKUWtyHJCDP+wsf0yoDhJVySyAtqv0ybK1AdOU6Rt0wmnZzt3Xio/Z5 O+1FsoWhQaOHVKvUX49CnKYEnP3jsU7Kcc0DIcPil1vD3+DTajt7cy9PvwH49czsyLdD jXxvUvtstC1BH34Qr7ZkXuuKigu1hetzJra1MPtMBbDrbG0cydAPEi4XcQOj6IZxd1lX sf6w== X-Received: by 10.152.29.133 with SMTP id k5mr24027973lah.44.1400620386365; Tue, 20 May 2014 14:13:06 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.205.73 with HTTP; Tue, 20 May 2014 14:12:26 -0700 (PDT) In-Reply-To: References: Date: Wed, 21 May 2014 06:12:26 +0900 X-Google-Sender-Auth: NuhIcOWI4LHy65X7YSNvXHn7qdw Message-ID: To: Nikita Popov Cc: Arvids Godjuks , PHP internals Content-Type: multipart/alternative; boundary=089e0158c8589838f904f9db5869 Subject: Re: [PHP-DEV] Re: 64bit and phpng, votes and plans From: yohgaki@ohgaki.net (Yasuo Ohgaki) --089e0158c8589838f904f9db5869 Content-Type: text/plain; charset=UTF-8 On Wed, May 21, 2014 at 5:45 AM, Yasuo Ohgaki wrote: > This is the reason why DB data values and Web inputs should not be > converted to native PHP data type blindly :) > It could work, but it cannot work with 64bit int. > It may be changed not to use int key (use string key) when int key overflows, then it would work. However, many users are trying to use strict type. Users may experience data validation errors for large int with 32bit int key. It would be better to allow 64bit int if int is 64bit. I prefer consistency, so array int key is better to support 64bit int key. IMHO. 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. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --089e0158c8589838f904f9db5869--