Scott Moore wrote:
Scott Moore wrote:
UCSD has the form:
close(filename, option)
Where option is a "word":
normal lock purge crunch
Note that a filename (not handle or var file reference) is used, and that "word" as option pretty much requires close to be a compiler built-in statement.
Ugh. So they are not even predefined constants?
[snip]
Using "word symbols" is actually the recommended method to use (standardwise) to prevent polluting the reserved tolken space. For example, "forward" and "external" are "word symbols". There are, or were, whole languages that work like that, leading to lots of ambiguous constructs.
Scott, I think you're getting your terminology mixed up. Word-symbol is the term both ISO standards use for those token spellings which are reserved solely for language syntatic use, e.g., "begin", "end", etc. are word-symbols. For "forward" (ISO 7185 and 10206), "interface" and "implementation" (ISO 10206), both standards use the term directive to refer to those spellings which have special language significance only in specified syntax slots and are spellings available for user defined uses outside those specified syntax slots.
Therefore, 'Using "word symbols"' is not the recommended method (standardwise) since it does pollute 'the reserved tolken space'.
Gale Paeper gpaeper@empirenet.com