3 ms·
This is also why capital letters are bad. It's easy to write code which fails to check for a capital letter, which leads to errors when subsequent code require
by kazinator 6y ago
This is also why capital letters are bad.
It's easy to write code which fails to check for a capital letter, which leads to errors when subsequent code requires a lower-case letter.
Capital letters are a billion dollar boondoggle.
It behooves languages to have a lower-case (or non-capital) character type which cannot be constructed with or assigned a capital letter.
- monoideism 6y agoMocking Tony Hoare - bold move: https://www.infoq.com/presentations/Null-References-The-Billion-Dollar-Mistake-Tony-Hoare/ https://www.infoq.com/presentations/Null-References-The-Bill...
- thrower123 6y agoIn all seriousness, after nulls, I think I've seen more issues caused by case-sensitivity in string comparisons than by any other class of error. Domain names. Email addresses. Windows UPNs. Windows filenames... All manner of LDAP shit.
- kazinator 6y agoMust have been before Unicode. :)
- smichel17 6y agoI always interpreted that quote to mean that implicit nullability was a mistake. It's fine to have nulls, but not five to have them pop up anywhere randomly. Capital letters are fine, but not if they randomly pop up when you thought you were only working in lowercase, and now suddenly all your string comparisons need a .toLoweR() on each side of the ==.