From 2dcbca3a7af41d8a678929a81752f8296c8b6245 Mon Sep 17 00:00:00 2001 From: Federico Ceratto Date: Mon, 14 Dec 2015 12:35:07 +0000 Subject: [PATCH] Updated Unofficial FAQ (markdown) --- Unofficial-FAQ.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Unofficial-FAQ.md b/Unofficial-FAQ.md index c7d599b..1b1264b 100644 --- a/Unofficial-FAQ.md +++ b/Unofficial-FAQ.md @@ -23,12 +23,13 @@ Most probably not. Reasons for avoiding them are: * "when false" is not a bad solution. At least syntax is still checked for deactivated code. * discard """ """" is another solution. -# Why is it case/style insensitive? +# Why is it case/underscore insensitive? * Identifiers which only differ in case are bad style. If the programming language treats them the same the programmer needs to come up with different names for different things. * Case insensitivity is widely considered to be more user friendly. This holds for file systems, configuration files, and programming languages. -* Many programming languages are case insensitive: Lisp, Basic, Pascal, Ada, Eiffel, Fortran. Since software for aircrafts and power plants has been written in Ada, it seems reasonable to assume that case insensitivity will not destroy civilisation. +* Many programming languages are case insensitive: Lisp, Basic, Pascal, Ada, Eiffel, Fortran. Since software for aircrafts and power plants has been written in Ada, it seems reasonable to assume that case insensitivity will not destroy civilization. * Note that most people confuse case sensitivity with case consistency (which is indeed good style). However, case consistency is easier to achieve with case insensitivity and a properly configured IDE than with case sensitivity. +* It prevents bugs: in large applications in other languages it's not uncommon to see bugs introduced by an incorrect completion, e.g. updatePlayerstatus / updatePlayerStatus / update_player_status. With case/underscore insensitivity you know in advance that there can be only one "updateplayerstatus" in your code (and write it in a consistent manner, e.g. always update_player_status) # Where can I find code examples?