[[ LCB ]] Update reference to adjust for changes in case-sensitivity rules.

runrevmark · runrevmark · commit 954c5a38a505 · 2015-03-19T09:19:14.000Z
diff --git a/docs/specs/livecode_builder_language_reference.md b/docs/specs/livecode_builder_language_reference.md
@@ -39,7 +39,7 @@ Strings use backslash ('\') as an escape - the following are understood:
 
 ## Case-Sensitivity
 
-At the moment, due to the nature of the parser being used, identifiers and keywords are all case-sensitive and keywords are reserved. The result of this is that, using all lower-case identifiers for names of definitions should be avoided.
+At the moment, due to the nature of the parser being used, keywords are all case-sensitive and reserved. The result of this is that, using all lower-case identifiers for names of definitions should be avoided. However, identifiers *are* case-insensitive - so a variable with name pFoo can also be referenced as PFOO, PfOO, pfoO etc.
 
 > **Aside:** The current parser and syntax rules for LiveCode Builder are constructed at build-time of the LiveCode Builder compiler and uses *bison* (a standard parser generator tool) to build the parser. Unfortunately, this means that any keywords have to be reserved as the parser cannot distinguish the use of an identifier in context (whether it is a keyword at a particular point, or a name of a definition).
 
@@ -56,7 +56,7 @@ It is highly recommended that the following naming conventions be used for ident
 
 By following this convention, there will not be any ambiguity between identifiers and keywords. (All keywords are all lower-case).
 
-> **Note:** The intent is that LiveCode Builder scripts will be case-insensitive like LiveCode Script; however this will require the Open Language parser infrastructure which is being developed for the next major version of LiveCode Builder.
+> **Note:** When we have a better parsing technology we will be evaluating whether to make keywords case-insensitive as well. At the very least, at that point, we expect to be able to make all keywords unreserved.
 
 # Typing
 
@@ -65,20 +65,18 @@ Modular LiveCode is a typed language, although typing is completely optional in
 The range of core types is relatively small, comprising the following:
 
  - **undefined**: the single value *undefined*
- - **boolean**: one of *true* or *false*
- - **integer**: any integral numeric value (size limitations apply)
- - **real**: any numeric value (size and accuracy limitations apply)
- - **number**: any integer or real value
- - **string**: a sequence of UTF-16 code units
- - **data**: a sequence of bytes
- - **list**: a sequence of any values
- - **array**: a mapping from strings to values
+ - **Boolean**: one of *true* or *false*
+ - **Integer**: any integral numeric value (size limitations apply)
+ - **Real**: any numeric value (size and accuracy limitations apply)
+ - **Number**: any integer or real value
+ - **String**: a sequence of UTF-16 code units
+ - **Data**: a sequence of bytes
+ - **List**: a sequence of any values
+ - **Array**: a mapping from strings to values
  - **any**: a value of any type
 
 Additionally, all types can be annotated with **optional**. An optional annotation means the value may be the original type or the undefined value.
 
-> **Note:** As it stands *any* does not include the undefined type and so *optional any* makes sense. There is an argument, however, that *any* should be implicitly optional as (technically) the undefined type is also a type. It is possible this aspect might be revised.
-
 > **Note:** The current compiler does not do type-checking; all type-checking happens at runtime. However, this is being worked on so there will soon be a compiler which will give you type errors at compile-time.
 
 # Modules
