Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:76831 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68300 invoked from network); 23 Aug 2014 06:21:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Aug 2014 06:21:43 -0000 Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.192.171 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.192.171 mail-pd0-f171.google.com Received: from [209.85.192.171] ([209.85.192.171:57152] helo=mail-pd0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1B/93-39740-5F238F35 for ; Sat, 23 Aug 2014 02:21:42 -0400 Received: by mail-pd0-f171.google.com with SMTP id z10so17131531pdj.16 for ; Fri, 22 Aug 2014 23:21:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type; bh=dmPwm9s1PT753DCnLwSFDKwFKHY6R1LysCanp+Bo6SM=; b=jLAcU/YfKadoGlmiomaitI4h6/XxqYju1MZ0tHAmWg3G8q0ezN/H17wsOLWYYxBspk qZWUm0aYEypw+mGTaXj1Mih7Rs7lbxhwH5xFphOEOBZEX3t3L7KYx/z2yhEEkdF0OLLJ 8iFosHyyEwpFxDedBzukChck/L2FUWJsnD5suxtps6ScyRn+ucubZ50CEDWOOI5gvKad B/NLPnudVp888bNjmAKHbjNhG/cHqBzq7LbwcuKxMK0CkDt23C8Cl5g0LTBALWMUeavQ 8qi6zCj+XBy91uBDN1um+VTOCVsoAdBkgpbZ6w1PGmsXskLt9IxxlymfnQ7mrX98n32t u3lQ== X-Gm-Message-State: ALoCoQn+Da4uX2ittQX7Xcc6icxefplpLPvw8eMqS2iL88khJsoIHU3qZQws3QTotu/hTMeIr/ho X-Received: by 10.70.35.67 with SMTP id f3mr11753896pdj.34.1408774898951; Fri, 22 Aug 2014 23:21:38 -0700 (PDT) Received: from [192.168.200.30] (c-50-131-44-225.hsd1.ca.comcast.net. [50.131.44.225]) by mx.google.com with ESMTPSA id tv3sm13789992pbc.39.2014.08.22.23.21.37 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 22 Aug 2014 23:21:38 -0700 (PDT) Message-ID: <53F832F0.7010601@lerdorf.com> Date: Fri, 22 Aug 2014 23:21:36 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Pierre Joye CC: PHP internals , Nikita Popov References: <53F7F6ED.1050609@lerdorf.com> <53F82F16.3030601@lerdorf.com> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="S0O5EK91Ub6Pgb93nCEArX6VkAWHE1weD" Subject: Re: [PHP-DEV] [RFC] Better type names for int64 RFC From: rasmus@lerdorf.com (Rasmus Lerdorf) --S0O5EK91Ub6Pgb93nCEArX6VkAWHE1weD Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 8/22/14, 11:09 PM, Pierre Joye wrote: > On Sat, Aug 23, 2014 at 8:05 AM, Rasmus Lerdorf wr= ote: >> On 8/22/14, 10:46 PM, Pierre Joye wrote: >>> In other words, it would be nice to see more developers actually >>> porting extensions to realize the amount of changes are introduced by= >>> NG and by the int64. The sooner is in order of magnitude must larger.= >>> It is not a bad comment, only a fact. Given that, before we choose to= >>> say that it is fine for one part to change APIs/Macros signatures or >>> names and not for another, we should really get a better view of what= >>> has actually changed. And how we can deal with our old habit to >>> maintain one tree for many major PHP versions. For many extensions, I= >>> do not think it will be possible, or with unreadable code with 2-3x >>> more #ifdef all over the place. >> >> I knew you would make this comparison. I am willing to suffer porting >> pain if it gets me a 20% performance boost. I am completely unwilling = to >> suffer any porting pain because Pierre has decided he doesn't like the= >> names of some macros. >=20 > Sorry Rasmus, this reply is irrelevant or off base. What in my reply > makes you tell that it is about my taste?=20 There is no technical reason to change IS_LONG to IS_INT along with the others in that category. It is purely a taste/purity/questionable-consistency thing and doesn't need to be done to solve any real technical problem. -Rasmus --S0O5EK91Ub6Pgb93nCEArX6VkAWHE1weD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org iEYEARECAAYFAlP4MvEACgkQlxayKTuqOuDvOwCfSE3wVuOat7q6PldO+eOfgPFq SEwAniO3OSbl832nVR2s0Vdh7HLWqiHW =wQdr -----END PGP SIGNATURE----- --S0O5EK91Ub6Pgb93nCEArX6VkAWHE1weD--