Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:76847 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 31256 invoked from network); 23 Aug 2014 20:13:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Aug 2014 20:13:46 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.46 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.216.46 mail-qa0-f46.google.com Received: from [209.85.216.46] ([209.85.216.46:32956] helo=mail-qa0-f46.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AB/B2-06800-9F5F8F35 for ; Sat, 23 Aug 2014 16:13:45 -0400 Received: by mail-qa0-f46.google.com with SMTP id v10so10889920qac.19 for ; Sat, 23 Aug 2014 13:13:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=QS5CvLDwn8QMgeLQrOkMRlm+Wywv2NhF9uZMdTeNnoc=; b=ZayHM3nCq5v0ya/67tb8iOjcSW2Ok7w4ECw/xiUmwLugaXuNrIWS67pq4NZdPyq5Bc VGPsfpEVqe4OTkfWpcEF4lEdkGIwZaUrmOAdfAerA6PPGviPKYesXH+eKFjHyVtbftgO WKN2Kdjdkci/Kj7fZqTuFw8bDJ1pSWy+gi+4ooqwWIdatM0Pbm99YjEaX5H/cocDplus 66VJhypdQTMzPHiwIxzeFslbtSXW5tHhB/QqLsGf+B5DwKcDTwDHkUjroGwo/BgOhS57 6Go3fXxhmnXtmOOOVj2uoCXNsZ60JIFM/bbKLKFhG3kbPsCnehe9RmhMz05t6sybi5Jb exqA== MIME-Version: 1.0 X-Received: by 10.140.106.225 with SMTP id e88mr19090951qgf.20.1408824823407; Sat, 23 Aug 2014 13:13:43 -0700 (PDT) Received: by 10.140.95.146 with HTTP; Sat, 23 Aug 2014 13:13:43 -0700 (PDT) In-Reply-To: References: <53F7F6ED.1050609@lerdorf.com> <53F82F16.3030601@lerdorf.com> <53F832F0.7010601@lerdorf.com> <53F8C3F2.1090009@lerdorf.com> <27CDAA74-FA13-43D3-809B-6F56D76AC5DE@ajf.me> Date: Sat, 23 Aug 2014 22:13:43 +0200 Message-ID: To: Andrea Faulds Cc: Kris Craig , Rasmus Lerdorf , PHP internals list Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] Better type names for int64 RFC From: pierre.php@gmail.com (Pierre Joye) On Sat, Aug 23, 2014 at 9:41 PM, Andrea Faulds wrote: > > On 23 Aug 2014, at 20:38, Pierre Joye wrote: > >> Please try to port one. That will solve this never ending ping pong >> game. Extensions are broken per se with ng, almost every zval macros >> usage must change (some disappeared, like the _PP ones), all hash APIs >> call must be change (a must, not detectable at compile time), etc. >> IS_LONG to IS_INT is a joke in comparison. But as nobody agrees on >> that, I won't discuss it to death. > > You previously told me on this list that if I maintained an extension, I= =E2=80=99d know that replacing macro names with a find/replace is a big dea= l. Excatly, and IS_LONG/INT are not macros and a very very tiny change in comparison to anything else, be ng alone, or ng+int64. >>> 2. If bigints are implemented, we=E2=80=99d have to rename everything a= gain. >> >> Ah, and that will be acceptable then, right? ;-) > > It wouldn=E2=80=99t be needless, it would be done to reduce confusion. > >> Also hurry up with that, even if not totally completed. Many >> extensions may have to deal with it and it will just double the >> porting work if it is not done soon. > > I=E2=80=99ll look into it. If you need help (windows or other), let me know. Want it in :) Cheers, --=20 Pierre @pierrejoye | http://www.libgd.org