Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71490 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 77408 invoked from network); 24 Jan 2014 09:43:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jan 2014 09:43:50 -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:33333] helo=klapt.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D3/5A-39789-4D532E25 for ; Fri, 24 Jan 2014 04:43:50 -0500 Received: by klapt.com (Postfix, from userid 33) id 8017923D60EC; Fri, 24 Jan 2014 10:43:45 +0100 (CET) Received: from 84.57.244.13 (SquirrelMail authenticated user anatol@belski.net) by webmail.klapt.com with HTTP; Fri, 24 Jan 2014 10:43:45 +0100 Message-ID: In-Reply-To: <52E17D63.4090300@oracle.com> References: <52E0F55F.4040802@lsces.co.uk> <2490044a0e2cba88044cf5da9b1b6647.squirrel@webmail.klapt.com> <52E17D40.8090001@oracle.com> <52E17D63.4090300@oracle.com> Date: Fri, 24 Jan 2014 10:43:45 +0100 To: "Christopher Jones" Cc: internals@lists.php.net 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 Chris, On Thu, January 23, 2014 21:36, Christopher Jones wrote: > > > On 01/23/2014 12:36 PM, Christopher Jones wrote: > > >> For reference, here is Anatol's mapping that allows extensions using >> the new types etc to compile with older PHP releases: >> https://github.com/php/php-src/blob/str_size_and_int64/compat/compat.h >> I would have leaned towards not requiring macro name changes, but I >> wouldn't vote against the RFC because of them. > > Anatol: what about creating the inverse of the compat.h #defines? Old > code can include those definitions and wouldn't need as many changes? > The macros are easy done of course, but the long/int keywords would conflict with the built-in types, wouldn't they? Well, if zpp var datatypes were still replaced, it should work. Is that what you mean? Regards Anatol