wrote in message news:064eafcb-e42f-cfeb-76f1-e2c5aec0e...@rhsoft.net...
Am 20.09.2017 um 11:30 schrieb Tony Marston:
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
jesus christ the german language DID NOT have a uppercase ß in the real
world until recently but had the lowercase ß virtually forever
how do you imagine "removeed from the list of valid characters" in that
case - frankly that paragraph above shows clearly that you should stop to
argue about this topic at all
Just because my opinion differs from yours does not give you the right to
demand that I stop expressing it.
To me the situation is quite simple.
- Human beings have grown accustomed to case-insensitive world, and to
remove this standard feature would cause great disruption.
- Some people may think that function names written as "do_something" or
"do_Something" or "Do_Something" which mean the same thing are wrong, but
that is no more than simply irritating for the nit-picking minority. If you
made those names mean different thing then that would be worse than wrong,
it would be criminally insane.
- Rather than making constants case sensitive it would be better to leave
then as case insensitive, but prevent the creation of a constant with the
same name but different case. This would make it consistent with function
and method names.
- If the use of some non-ASCII characters in function names causes case
folding problems then I see two choices - either disallow non-ASCII
characters in function names, or allow Unicode characters but disallow any
which have case folding problems.
Simply telling me that it would be easier to make the entire language case
sensitive as there are "difficulties" with case folding of a minute number
of unicode characters is not good enough. Programmers are supposed to solve
problems for their users, not create them.
--
Tony Marston
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
