Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:100628 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 20129 invoked from network); 15 Sep 2017 14:38:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Sep 2017 14:38:38 -0000 X-Host-Fingerprint: 62.31.75.76 76.75-31-62.static.virginmediabusiness.co.uk Received: from [62.31.75.76] ([62.31.75.76:10575] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 91/7F-19300-EE5EBB95 for ; Fri, 15 Sep 2017 10:38:38 -0400 Message-ID: <91.7F.19300.EE5EBB95@pb1.pair.com> 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> <8bbcc1fc-0d13-27d4-a04f-0a5ebda4c32e@rhsoft.net> In-Reply-To: <8bbcc1fc-0d13-27d4-a04f-0a5ebda4c32e@rhsoft.net> Date: Fri, 15 Sep 2017 15:38:33 +0100 Lines: 6 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Newsreader: Microsoft Windows Live Mail 16.4.3564.1216 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3564.1216 X-Posted-By: 62.31.75.76 Subject: Re: [PHP-DEV] Deprecate and remove case-insensitive constants? From: TonyMarston@hotmail.com ("Tony Marston") wrote in message news:8bbcc1fc-0d13-27d4-a04f-0a5ebda4c32e@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 While that may be "uncool" or even "inconsistent" it does not cause a genuine problem. But you seem to be supporting a change which would be worse than uncool, it would be downright horrific. No human language that I know of allows a word to change its meaning just by changing the case of one or more characters, and this standard behaviour was echoed in all the computer systems that I have used since the 1970s. The fact that I can create a function called do_something() and later refer to it as either Do_something(), do_Something() or even Do_SomeThing() may be annoying but it is irrelevant. Do you realise how many problems it would cause if each change in case pointed to a totally different function? Would you support anyone who proposed adding a series of functions to PHP core or an extension where every function used exactly the same words but in a different case? What will happen in the future if we move away from keyboard input towards speech input? It will not be good enough to simply say a word, you would have to spell it out character by character and specify the case of each character. Do you think that would be a good idea? >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 I'm afraid that changing the way I do things just to be "consistent" with others is not a good argument when it ends up being "consistently bad". >-------- 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. -- Tony Marston