JM 12/19/11: For now I don't think there is any good place to put this information in the main docs. Once we get back to the Basic documentation project, it can be integrated into the table of reserved words/functions/features/statements/etc. we were building.
Compiler/language refinement: As an aide to developers looking to use COMPIL /X:2 to take advantage of newer language extensions but being held back by conflicts with new reserved words, the compiler now allows the following previously reserved words (functions) to be used as names of scalar (non array) variables:
EDIT, EDIT$
ERRMSG
FILL, FILL$
PAD, PAD$
STRIP, STRIP$
XFUNC, XFUNC$
Also, the previously reserved words INPUTONLY and OUTPUTONLY may now be used as variables (scalar or otherwise).
Note that while this deviates from the AMOS BasicPLUS compiler's rejection of these keywords as illegal for scalar variable names, the deviation seems harmless and indeed, removes a stumbling block for developers who unknowingly used these words as variable names. AlphaBASIC has always distinguished between scalar and array variables with the same name, and since the above system functions use the same syntax as arrays, it seems only logical to distinguish them as well.
The change affects only the compiler; it has no effect on RUN files or backwards RUN compatibility.
