Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:91290 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 99320 invoked from network); 18 Feb 2016 21:41:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Feb 2016 21:41:33 -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.124 cause and error) X-PHP-List-Original-Sender: php@fleshgrinder.com X-Host-Fingerprint: 212.232.28.124 mx203.easyname.com Received: from [212.232.28.124] ([212.232.28.124:60031] helo=mx203.easyname.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E1/61-27267-B8A36C65 for ; Thu, 18 Feb 2016 16:41:32 -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 1aWWKG-0000yP-CZ for internals@lists.php.net; Thu, 18 Feb 2016 21:41:28 +0000 Reply-To: internals@lists.php.net References: <56C63852.3060803@gmail.com> To: internals@lists.php.net Message-ID: <56C63A7D.4000005@fleshgrinder.com> Date: Thu, 18 Feb 2016 22:41:17 +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: <56C63852.3060803@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal From: php@fleshgrinder.com (Fleshgrinder) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2/18/2016 10:32 PM, Stanislav Malyshev wrote: > Hi! > >> I'd like to propose an RFC to deprecate and eventually remove the >> "var" keyword. > > Don't see much point - it is the same as public and doesn't hurt > anyone. Removing it does not improve any code in any way, just > makes it harder to upgrade. > Although it is true that an upgrade from PHP 7 to 8 will involve more work, it is not true that it does not hurt anyone. This is a well known problem in design: https://www.nngroup.com/articles/reduce-redundancydecrease-duplicated-de sign-decisions/ This is about UI but the same principles apply to aliased functionality in a programming language: - - "What is the difference between *implode* and *join*?" - http://stackoverflow.com/questions/17914008 - http://www.php-questions.com/phpfaq/answer124 - http://rajeshstutorials.blogspot.de/2012/01/difference-between-join-and- implode-in.html - ... - - "What is the difference between *die* and *exit*?" - http://stackoverflow.com/questions/1795025 - http://stackoverflow.com/questions/12702875 - https://phillipnb.wordpress.com/2012/03/21/die-and-exit/ - https://www.quora.com/Is-there-any-difference-between-die-and-exit-in-PH P - ... - - "What is the difference between *is_writable* and *is_writable*?" - - "What is the difference between ...?" It confuses users and wastes their time. - -- Richard "Fleshgrinder" Fussenegger -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWxjp9AAoJEOKkKcqFPVVr93cP/1lE2Cxu3TRNsDybFB+3YnmN nP6mZlApj8cPT6Q8/P6YnwKb2NZ2X9G/IuYCXzhLUTULkmiZxhxhUzPzfT3a99F9 DIHg8u+ZpOwn3baZdUJsxWouYxLtUS6mJb9BBnkvbhCklNWlX8q7A/JN/gxmm2vi PXcLh/gEUE0D+z2+aIO5ozv7kzbk7gf0fiX1gAnnor+ACozlBHPxgO/QMLl0V9RL Xj5jOhUIMXO6tWowmNxsSgDGHfhHD74G6AVBN/aJvqiWSfPpHEF8ZMyXuVg/BarL 9lVcBw6Hws/n40uTh/lMxo7exkAV4X8wBc0FkXPNVvYhuwivNBwsF1eO43MWT+5b pKPAIcjyrbEOeb0CFegHRLr2Vw8g0t/VWz70LV445JgrDS9R/VicjUApRKER+blK A6QF/K4cPtq12npNA+vFOk0o93L1tzaRakn33jk+m9wypQMqEJD/sZvbE4YVnlkB B1c9lJJGLp/KR27iRz26+dUn+PRvL2zPT1mFk6HXoYpSHDJNLT5F5N+fgnp/Dq8n mZmQ/Uhz2cc6/b+IVIDP18x8XKklZe103a0sCb0NVkB6WYL/Qc7S5Y/acMGmLxiJ HhvSU6bkE0lSuzUYptmyQ+Uy/J+ChtTRjxOKHHSVR5ZCTrTKYyLuyoH56nREUiEo KPp+WLmzxqgGDEEt33uk =YHLQ -----END PGP SIGNATURE-----