wrote in message news:ba7ed73b-8547-2029-7344-6705a70c6...@rhsoft.net...
Am 15.09.2017 um 16:38 schrieb Tony Marston:
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
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
None of the IDEs that I have used have enforced such a rule, neither have
any languages, so it is an artificial rule invented by someone who doesn't
now how to provide a proper solution.
As I have said in several other posts, the vast majority of the human race
has come to accept case-insensitive software, and if you can't implement it
then you should step aside and make room for someone who can.
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
You seem to misunderstand the term "rocket science" which means that
something is so difficult that it can only be done by a highly trained
individual. Something which is NOT rocket science is supposed to be so easy
that anyone can do, not just a scientist.
People keep telling me that switching between upper and lower case for all
character sets in the universe is not 100% simple because of a small number
of exceptions. So what? Identify the exceptions and write code which deals
with them. If we only wrote deal to deal with the easy stuff there would be
no need for highly skilled programmers as anyone could do it.
--
Tony Marston
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
