Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:100618 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 94107 invoked from network); 15 Sep 2017 09:54:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Sep 2017 09:54:05 -0000 Authentication-Results: pb1.pair.com header.from=lists@rhsoft.net; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=lists@rhsoft.net; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain rhsoft.net designates 91.118.73.15 as permitted sender) X-PHP-List-Original-Sender: lists@rhsoft.net X-Host-Fingerprint: 91.118.73.15 mail.thelounge.net Received: from [91.118.73.15] ([91.118.73.15:36073] helo=mail.thelounge.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FA/CB-19300-933ABB95 for ; Fri, 15 Sep 2017 05:54:03 -0400 Received: from srv-rhsoft.rhsoft.net (Authenticated sender: h.reindl@thelounge.net) by mail.thelounge.net (THELOUNGE MTA) with ESMTPSA id 3xtrMT6zjtzXMv for ; Fri, 15 Sep 2017 11:53:57 +0200 (CEST) To: internals@lists.php.net References: <3D.0C.10715.383F8B95@pb1.pair.com> <1505382004.4078127.1105791680.3A06C2FA@webmail.messagingengine.com> <16.4C.19300.B2D7AB95@pb1.pair.com> <7394E3CE-B05A-474E-8AB5-A651FDD35232@gmail.com> <47.8F.19300.9988AB95@pb1.pair.com> <1505397937.4137791.1106049000.16B8878B@webmail.messagingengine.com> <66.C9.19300.D999BB95@pb1.pair.com> Message-ID: <8bbcc1fc-0d13-27d4-a04f-0a5ebda4c32e@rhsoft.net> Date: Fri, 15 Sep 2017 11:53:57 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <66.C9.19300.D999BB95@pb1.pair.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-CH Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Deprecate and remove case-insensitive constants? From: lists@rhsoft.net ("lists@rhsoft.net") Am 15.09.2017 um 11:12 schrieb Tony Marston: > I am not asking the world to slow down because I am too lazy to change. > I am arguing that case insensitive software has been around for many > decades, and for some people to advocate for its removal just because > they don't have the brain power to come up with a proper solution for a > minor glitch that affects only a small number of languages I find > unacceptable. A competent programmer would fix the problem that affects > the few without removing a feature that the many are used to and a competent programmer using PHP as programming language would not define a funtion do_something() and write "Do_Something", "do_Something", "DO_something" all over his codebase the problem which makes such a change dramatic is the poor code quality of most projects and as i remeber you even fighted some months ago that a consistent coding style within a project is nothing you care about and that explains how you argue here very well -------- Weitergeleitete Nachricht -------- Betreff: Re: [PHP-DEV] Class Naming in Core Datum: Mon, 5 Jun 2017 09:14:47 +0100 Von: Tony Marston An: internals@lists.php.net Seriously, can you explain in words of one syllable the precise benefits of such a consistency? Can you measure the benefits? Just because some OCD sufferers like consistency is not a good enough reason. I have been programming for over 30 years, and in that time I have had to deal with both snake_case and CamelCase, and while I personally find that snake_case is more readable, especially with names that contain more than 3 or 4 words, I have no trouble reading either. Having a mixture of styles does not cause a problem (except in the minds of OCD sufferers) so IMHO it does not require a solution. Anybody who says that they cannot work with a mixture of naming styles is either a liar or Illiterate.