Date: Fri, 1 Feb 2019 08:00:16 +0000
From: Harald van Dijk <[email protected]>
Message-ID: <[email protected]>
| I was referring to the second token on the second line, which is foo,
| not foo=bar.
Oh, sorry, I was in too much of a rush this morning, and did not
read all that carefully (or really, at all...)
For that I might, if some different wording to what is currently
proposed is needed, use something like:
* the TOKEN is the first token observed, or follows other
tokens which would allow this TOKEN to become the command
word of a simple command [xref], should the (unrecognised
yet) following tokens (if any) allow the token sequence
to be parsed that way, but regardless of what tokens follow.
I think this also is compatible with your concern about using tokens
rather than characters (wharacters are never relevant to parsing, so
I'd suggest not confusing things by switching to that lower level
terminology).
kre
