Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74389 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19769 invoked from network); 20 May 2014 21:17:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 May 2014 21:17:34 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.67 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.67 smtp67.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.67] ([108.166.43.67:42010] helo=smtp67.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E4/E1-08771-D66CB735 for ; Tue, 20 May 2014 17:17:34 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp1.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 05B06149752; Tue, 20 May 2014 17:17:31 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp1.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 7BB03149746; Tue, 20 May 2014 17:17:30 -0400 (EDT) Message-ID: <537BC669.2030704@sugarcrm.com> Date: Tue, 20 May 2014 14:17:29 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Yasuo Ohgaki , Nikita Popov CC: Arvids Godjuks , PHP internals References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: 64bit and phpng, votes and plans From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > 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. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227