SIC EXTENSION .class and Sic EXtension .class are equivalent
but not SIC EXTENSION .CLASS
A pending question is whether a slash can begin a string without double
quotes. This would allow file names to be typed directly, but would
prevent the user of being warned by an error message in case of mistyped
Robert Lucas and Stephane Guilloteau propose that
- Single slash necessarily begins an option
- Double slash can be used to begin an absolute path/file name
file out /usr /new ! Returns error "No such option /usr" file out /usr/toto/new ! Returns error "No such option /usr/toto/new" file out //usr/toto /new ! Creates file /usr/toto (option /new) file out "/usr/toto" /new ! Creates file /usr/toto (option /new)4 voted in favor, 2 against (noting that double slash creates unecessary exception, quotes can be used instead), 2 did not comment. This issue is still pending (there is no programming problem).
SAY "toto = ""toto""!"will result in
toto = "toto"!
This cleans up a previously strange behaviour, which gave error message,
but still produced some (clumsy) output.
command "toto"TATA"titi" ! command "toto"'TATA'"titi" ! command "toto"/titi ! command "toto"+titi ! command "toto"titi !are all invalid, and recognized as such at parsing time.
command "toto"'titi' ! TITI is a known variableis valid (because titi is a known variable), but
command "toto"'titi' ! TITI is NOT a variable command "toto".eq. !are both invalid, but recognized only as such at execution time.