Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71062 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 92051 invoked from network); 11 Jan 2014 14:48:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Jan 2014 14:48:28 -0000 Authentication-Results: pb1.pair.com header.from=ab@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=ab@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.214.73.107 as permitted sender) X-PHP-List-Original-Sender: ab@php.net X-Host-Fingerprint: 85.214.73.107 klapt.com Received: from [85.214.73.107] ([85.214.73.107:55155] helo=klapt.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 29/D2-10544-9B951D25 for ; Sat, 11 Jan 2014 09:48:27 -0500 Received: by klapt.com (Postfix, from userid 33) id 2DF6C23D6080; Sat, 11 Jan 2014 15:48:22 +0100 (CET) Received: from 188.110.167.245 (SquirrelMail authenticated user anatol@belski.net) by webmail.klapt.com with HTTP; Sat, 11 Jan 2014 15:48:22 +0100 Message-ID: <10f19e40b03ee19837010a988eb05706.squirrel@webmail.klapt.com> In-Reply-To: References: Date: Sat, 11 Jan 2014 15:48:22 +0100 To: "Jakub Zelenka" Cc: "Hannes Magnusson" , "Nikita Popov" , "PHP Developers Mailing List" Reply-To: "Anatol Belski" User-Agent: SquirrelMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC] 64 bit platform improvements for string length and integer From: ab@php.net ("Anatol Belski") Hi Jakub, On Sat, January 11, 2014 14:18, Jakub Zelenka wrote: > Hi Anatol, > > > > >> >> About zpp I've got a click - the compatibility with 5.x can be >> integrated into zpp itself in 6.x. I mean look here >> >> http://git.php.net/?p=php-src.git;a=blob;f=Zend/zend_API.c;hb=refs/head >> s/str_size_and_int64#l326 - 'l' and 'L' was replaced with 'i' and 'I', >> but nothing prevents to turn those formats as aliases in 6.x. That way >> 'l' and 'i' and another pairs >> will do the same thing, new implementations can use clean semantics, and >> the old formats can be removed after 5.x EOL. This solution however >> won't force the new semantic. >> > > I agree with keeping old flags ('l', 'p', 's'...). I think that would be > good to add range checks to zend_parse_arg_impl for these flags. If the > casted value is bigger (LONG_MAX, INT_MAX...), then warning. It would be > really helpful and simplify the migration for library wrappers where > these checks needs to be usually done... > the range checks is what 'L' vs 'I' would stand for, the 'L' would be available as alias for 'I', so one don't has to change zpp. A good thing were to add type checks, with gcc http://gcc.gnu.org/onlinedocs/gcc/Typeof.html , however not sure it's available with Visual Studio. Regards Anatol