Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67597 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 79392 invoked from network); 31 May 2013 19:33:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 May 2013 19:33:27 -0000 Authentication-Results: pb1.pair.com header.from=derick@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=derick@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 82.113.146.227 as permitted sender) X-PHP-List-Original-Sender: derick@php.net X-Host-Fingerprint: 82.113.146.227 xdebug.org Linux 2.6 Received: from [82.113.146.227] ([82.113.146.227:49498] helo=xdebug.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 61/FE-02347-50BF8A15 for ; Fri, 31 May 2013 15:33:26 -0400 Received: from [10.21.1.104] (php.xs4all.nl [83.163.231.87]) by xdebug.org (Postfix) with ESMTPSA id 8D07DDE151; Fri, 31 May 2013 20:33:22 +0100 (BST) User-Agent: K-9 Mail for Android In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Date: Fri, 31 May 2013 21:33:17 +0200 To: Anthony Ferrara ,"internals@lists.php.net" Message-ID: <6dae6c81-3e50-42f3-9a7e-87eedf8861d4@email.android.com> Subject: Re: [PHP-DEV] 5.NEXT Integer and String type modifications From: derick@php.net (Derick Rethans) Anthony Ferrara wrote: > I want to start an idea thread (or at least get a conversation going) > about > cleaning up the core integer data type and string lengths. Here's my > ideas: > > 1. Change string length in the ZVAL from int to size_t > - http://lxr.php.net/xref/PHP_5_5/Zend/zend.h#321 > 2. Change long in the ZVAL (lval) to a system-determined 64bit fixed > size In principle I think this is great thing to do. Not having a 64 bit type is annoying. I'm a bit curious on how this is going to work with all sorts of object wrappers that are now in place as workaround. And casting int64 to int32 needs to very well looked at as well. Derick