wrote in message news:098adca8-6897-929d-90e4-cc464f0e2...@rhsoft.net...
Am 19.09.2017 um 11:24 schrieb Tony Marston:
If the single character "ß" represents two "s" characters joined
together, then the uppercase equivalent should also be a single character
which looks like two "S" characters joined together. If it is not
possible to write code which deals with these exceptions, then one
alternative would be to remove these exceptions
remove from where?
from the reality?
If the lowercase character "ß" causes so many problems because it has no
proper equivalent in uppercase then it should be removed from the list of
valid characters. Either that or provide a single uppercase character -
which is what that wikipedia article you quoted says actually happened this
year.
have fun, it becomes even more complexer and currently it's in discussion
where to place the uppercase on a keyboard
https://en.wikipedia.org/wiki/%C3%9F#Capital_form
> If the single character "ß" represents two "s"
no, until short ago there where just no uppercase one and that's only about
german - you still missed *to prove* "Removing case insensitivity
completely is not a proper solution as it removes a feature that we humans
have been used to for decades"
When we search for a word in a dictionary we do not need to specify case as
that is irrelevant, so "sausage" is the same as "SAUSAGE". There are words
which can have different meanings depending on the context, such as "this
cup is made of china" and "I am going to China", but provided that the
context remains the same then case is irrelevant.
When it comes to software case insensitivity has been the standard since day
1. When searching for a file in MS Windows you do not have to specify case
as it is not possible to have different files with the same name but
different mixtures of case.
When searching for a word or phrase in a text editor it is not necessary to
specify case, although some editors include an option to make the search
case sensitive.
since i know nobody right in his mind which writes inconsistent code where
this is a real world problem and if someone writtes "my_function",
"MY_function" and "my_Function" in his code and don#t stop that nosnese he
simply get fired
That may be uncool, but the only problem it causes is in the tiny minds of
OCD sufferers. By making the language case sensitive and allowing
"my_function", "MY_function" and "my_Function" to be defined as separate
functions with separate implementations would be inviting total disaster.
--
Tony Marston
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
