tuple: a logical ordered union of several elements; when a tuple is placed into the data stack, the rightmost element in writing is the topmost on the stack, and floating-point numbers are placed into the floating-point stack.
lexeme: a syntactic unit of a program (a Forth source code); (unless otherwise noted, it is a sequence of non-blank characters delimited by a blank).
to recognize a lexeme: to determine the interpretation semantics and the compilation semantics for the lexeme in the current dynamic context.
to interpret a lexeme: to perform the interpretation semantics for the lexeme in the current dynamic context.
to compile a lexeme: to perform the compilation semantics for the lexeme in the current dynamic context.
to translate a lexeme: to interpret the lexeme if interpreting, or to compile the lexeme if compiling.
dynamic context of a lexeme: information that is available at the time the lexeme is translated.
unqualified token: a tuple of data objects that determines the interpretation semantics and the compilation semantics for a lexeme in its dynamic context.
token: unqualified token (a synonym, when it is clear from context).
to interpret a token: to perform the interpretation semantics that are determined by the token.
to compile a token: to perform the compilation semantics that are determined by the token.
to translate a token: to interpret the token if interpreting, or to compile the token if compiling.
token translator: a Forth definition that translates a token; also, depending on context, an execution token for this Forth definition.
resolver: a Forth definition that tries to recognize a lexeme producing a tuple of a token and its token translator.
token descriptor object: an implementation dependent data object (a set of information) that describes how to interpret and how to compile a token.
token descriptor: a value that identifies a token descriptor object; also, less formally and depending on context, a Forth definition that just returns this value, or a token descriptor object itself.
fully qualified token: a tuple of a token and its token descriptor.
recognizer: a Forth definition that tries to recognize a lexeme producing a fully qualified token.
simple recognizer: a recognizer that may produce the same token descriptor only.
compound recognizer: a recognizer that can produce the different token descriptors.
perceptor: a recognizer that is currently used by the Forth text interpreter to translate a lexeme.
current recognizer: the perceptor (an unformal synonym).
default perceptor: the perceptor before it was changed by a program (or after reverting these changes).
Short URL: https://git.io/JfhaI
Short ULR to the file of comparison: https://git.io/JfjoJ
The latest version of this term definitions file is in the dedicated repository: terms-and-datatypes.md (some rationales in Issue#2).
Perhaps we don't need the both terms: "tuple" and "token". It seems, the term "tuple" is enough.