Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:100629 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21794 invoked from network); 15 Sep 2017 14:48:06 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Sep 2017 14:48:06 -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:43615] helo=mail.thelounge.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A4/CF-19300-428EBB95 for ; Fri, 15 Sep 2017 10:48:06 -0400 Received: from srv-rhsoft.rhsoft.net (Authenticated sender: h.reindl@thelounge.net) by mail.thelounge.net (THELOUNGE MTA) with ESMTPSA id 3xtytn09FczXMb for ; Fri, 15 Sep 2017 16:48:00 +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> <8bbcc1fc-0d13-27d4-a04f-0a5ebda4c32e@rhsoft.net> <91.7F.19300.EE5EBB95@pb1.pair.com> Message-ID: Date: Fri, 15 Sep 2017 16:48:00 +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: <91.7F.19300.EE5EBB95@pb1.pair.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-CH Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Deprecate and remove case-insensitive constants? From: lists@rhsoft.net ("lists@rhsoft.net") Am 15.09.2017 um 16:38 schrieb 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 i brought you samples of german where the meanining of the same word changes *dramatically* - "nett zu Vögeln" versus "nett zu vögeln" which goes from "nice to birds" to "nice to fuck" > 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? only when one is so short-sighted as you act it's not rocket science at compile time throw a error that you are not allowed to define foo() and Foo() in the same software which has no runtime costs and after that you may even have less runtime costs because all the case-insensitive handling can be skipped and well, for the time of deprecation the compiler code with finally throws errors can issue the warnings with file and line - i assure you that going to fix that warnings takes less time than the whole discussion with you over the last days from several people > 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? see above - just because you assume it's rocket scienece doesn't mean it is