wrote in message news:8bbcc1fc-0d13-27d4-a04f-0a5ebda4c...@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 <tonymars...@hotmail.com>
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
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
