Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:91412 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96393 invoked from network); 25 Feb 2016 18:11:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Feb 2016 18:11:04 -0000 Authentication-Results: pb1.pair.com smtp.mail=php@fleshgrinder.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=php@fleshgrinder.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain fleshgrinder.com from 212.232.28.126 cause and error) X-PHP-List-Original-Sender: php@fleshgrinder.com X-Host-Fingerprint: 212.232.28.126 mx205.easyname.com Received: from [212.232.28.126] ([212.232.28.126:46472] helo=mx205.easyname.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5A/E2-11730-5B34FC65 for ; Thu, 25 Feb 2016 13:11:04 -0500 Received: from cable-81-173-133-29.netcologne.de ([81.173.133.29] helo=[192.168.178.20]) by mx.easyname.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84) (envelope-from ) id 1aZ0NP-0001oU-3h for internals@lists.php.net; Thu, 25 Feb 2016 18:10:59 +0000 Reply-To: internals@lists.php.net References: <56C77575.4090906@fleshgrinder.com> <56C77FC8.1070500@gmail.com> <56C78496.9020804@fleshgrinder.com> <56CB6BA7.8060500@gmail.com> <56CDEB49.5040006@fleshgrinder.com> <74.A1.29886.2C8CEC65@pb1.pair.com> To: internals@lists.php.net Message-ID: <56CF439F.2040506@fleshgrinder.com> Date: Thu, 25 Feb 2016 19:10:39 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <74.A1.29886.2C8CEC65@pb1.pair.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="LsKiWqmuHwiDmjgI7nE3KkEFCq6AMBv5g" Subject: Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal From: php@fleshgrinder.com (Fleshgrinder) --LsKiWqmuHwiDmjgI7nE3KkEFCq6AMBv5g Content-Type: multipart/mixed; boundary="HtcngomedkJKcgjsnnDww4fAS9GEPwhwQ" From: Fleshgrinder Reply-To: internals@lists.php.net To: internals@lists.php.net Message-ID: <56CF439F.2040506@fleshgrinder.com> Subject: Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal References: <56C77575.4090906@fleshgrinder.com> <56C77FC8.1070500@gmail.com> <56C78496.9020804@fleshgrinder.com> <56CB6BA7.8060500@gmail.com> <56CDEB49.5040006@fleshgrinder.com> <74.A1.29886.2C8CEC65@pb1.pair.com> In-Reply-To: <74.A1.29886.2C8CEC65@pb1.pair.com> --HtcngomedkJKcgjsnnDww4fAS9GEPwhwQ Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2/25/2016 10:26 AM, Tony Marston wrote: >> Science shows that it is harmful, let's clean it up! >=20 > Your "proof" is not scientific, it is just personal opinion. There is n= o > evidence that use of the "var" keyword is harmful in any way. I think the diverged from talking about the "var" keyword in particular towards duplication in general a long time ago. However, I still think that DRY is empirically proven. > Where is your proof? You say "not used by a major part of the community= " > which means that it is still being used by a minor part, but exactly ho= w > "minor"? I don't see why I should be forced to make a totally > unnecessary change to vast numbers of my scripts just to fall in line > with your personal opinions. It is true that I did not provide this proof because Colin O'Dell did claim this fact in the very initial message of this thread and I believe him. > There is no reason to remove it from ANY version of PHP. It does no > harm, it would take effort to take it out and amend the documentation, > but for what benefit? I stick to the main reason I gave, DRY. Duplication needs to be managed and removing it removes the maintenance burden. > Change for change's sake is never a good idea. I have been developing i= n > several languages for 40 years, and I can tell you point blank that > while programmers expect new features to be added they do NOT expect ol= d > features to disappear. Once a piece of code has been written and has > proved to work as designed it is expected to work with all future > versions. The only exception to this is to plug holes in security. This= > is called "forwards compatibility", and was a major selling point of al= l > my previous languages. If developers fear that they will have to rewrit= e > huge swathes of code each time a new version is released they will > quickly give up and move to a "professional" language which offers long= > term stability. I did not say that we should change for change's sake. I only stated that trying hard to prevent change by all means is wrong. Again, this diverged away from the "var" keyword alone a long time ago and was more a general statement. TL;DR Thanks for yet another aggressive/provocative email, I stick to my +1. However, you all have valid points to keep it. --=20 Richard "Fleshgrinder" Fussenegger --HtcngomedkJKcgjsnnDww4fAS9GEPwhwQ-- --LsKiWqmuHwiDmjgI7nE3KkEFCq6AMBv5g Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWz0OkAAoJEOKkKcqFPVVrwl0QAIMFTYEGDw9qJJJFnFC3Ob2h 1gD16NVX/+bPls78JfcEOsadJtrxhRNXSTlomsfE+LxH4W8H831STjftJQDRyd+E j2xIG6QoMwAxnG1GO3YfLTrQX5t2E97j76GGIVOteM9BlXeeqctfPMB5TSDtqBB9 UhCaX6MP/DgcvCkDBW3K8ZtRvgIn4QRM3Mw5asLOuIhJoQJcPkbYp9iomWQT1EO3 B+U2inc33GFlnZmZlh+jZ2qgyE3MH5hnywQWkQ3mgkBhcvvsiQFaTKeFuTxQp1Lx p4FlFMNWvJK6S/97rqcCNCB5H1VAtaPW+kLvcgdf/SdzGVGzTO1xaQq2Iq7lyK6U Al0KwKshSmCAco2TwiLOiiMMJcOZKIrVTi1mq/zJtzQiaOGjLaEp3Z+ISdFQ5qdC zJzNWYqSFeW37hAyp6CV5qncYhrfIdbkcXWaB+jmoUZkWs/MGw0Xkkcm6+1nZMiY w3wFk456p70Vuf/bOR8UMkbgAWXkc3sEZzBVcfh8HRmigPafEDNI2rFgfJYAjUvl o5UJMB1Zft76gPSRSCKx9zVjuJEm1euR1IG2cMjZRh1WGAwuCJNPMV9vMVe8ERVk mjImBqtpPhz31GuBxErY66vc8BnS80X9XB4L9gNR7jLnE0xbUe2mhJ2AzVaDTbua niMR6Y1Q/aL2xyvz0mCP =tZ+2 -----END PGP SIGNATURE----- --LsKiWqmuHwiDmjgI7nE3KkEFCq6AMBv5g--