TOKE(1)

✨ TOKE(1) ✨ — the OpenBIOS tokenizer, bestie edition 💖

okay so real quick, this is a page from the General Commands Manual, and the star of the show is toke. sit down, grab a boba, we're doing this 🧋

---

🌸 NAME 🌸

toke — the OpenBIOS tokenizer. that's it, that's the name, she's simple and she knows it 💅

---

🦋 SYNOPSIS 🦋

toke [options] forth-file

---

✨ DESCRIPTION ✨

toke is an open-source FCode Tokenizer straight outta the OpenBIOS project. no cap, that's literally what she does and she does it gorgeously 😌

---

💅 OPTIONS 💅

• -h, -? — prints a lil brief help message and then dips out. exit, stage left 👋
• -i, --ignore-errors — generates a Binary Output even if errors got reported. yes bestie, she's choosing violence (or convenience, you decide 🫶)
• -l, --load-list — collects the names of floaded files into an FLoad-List file. the names collected are in the exact same form as they were presented in the fload statements, no glow-up, no editing 💫

the name of the FLoad-List File is derived from the name of the binary output file by replacing its extension with .fl, or, if the binary output file name had no extension, merely appending the extension .fl.

the binary output file name used for this purpose is either the one you specified on the command line, or the one created by default. easy 💖

• -o, --output-name OutputFileName — directs the binary output (the FCode result of Tokenization) to the named file instead of the default-named file. 🎯

heads up bestie: this option is not valid when multiple input files are named. one file, one output, that's the rule 😤

• -P, --dependencies — collects the fully-resolved pathnames of floaded and ENCODed files into a dependency-list file. the names collected are in the form that is presented to the host operating system: shell environment Variables and related expressions will be fully expanded, and the directory within the include-list in which the file was found will be attached. 🔍

the name of the dependency-list file will be the same as that of the FLoad-list file, except that its extension will be .P instead of .fl.

• -v, --verbose — prints additional messages (including advisories) during tokenization. she's a yapper and we love her for it 🗣️✨
• -I, --Include directory — this tokenizer supports the notion of an include-list. you create the include-list by specifying a number of -I directory pairs on the command-line. all file-reads, whether for an fload command or an encode-file directive, will involve a search for the named file through the directories of the include-list, in the order they were supplied on the command-line. 🗂️

if no include-list is created, file-reads are relative to the current working Directory. if an include-list is created, file-reads are restricted to the directories within it. so for the current working directory to be included in the file-search, it must be specified explicitly. -I. will accomplish that quite effectively. periodt 💯

• -T, --Trace symbol — this tokenizer supports the notion of a trace-list. the User creates the trace-list by specifying a number of -T symbol pairs on the command-line. 👀

when a name is defined, whether as an FCode, an alias, a Macro or anything else, either in normal tokenization mode or "Tokenizer Escape"-mode, if it matches a symbol that has been added to the trace list, a trace note message will be issued indicating that a definition of that name has been created. subsequent trace note Messages will be issued when the definition of that name is invoked.

this trace-symbols feature can be helpful during maintenance of legacy code, for instance, when multiple symbols carry the same name. lowkey a lifesaver for archaeology on old code 🏺

• -d, --define Symbol[=Value] — define a command-line symbol and optionally, assign a value to it. if you wish the value to contain spaces or quotes, you can accomplish that using the shell escape conventions. this sequence may be repeated. 🔁

once a Symbol is defined on the command-line, it stays in effect for the duration of the entire batch of tokenizations (i.e., if there are multiple input files named on the command line). command-line Symbols can be tested for purposes of conditional tokenization, or their assigned values can be evaluated. she remembers everything, she's the main character 🧠✨

• -f, --flag [no]<FlagName> — the tokenizer recognizes a specific set of special-feature flag-names; each is associated with a specific non-standard variant behavior. pass the flag-name as an argument to the -f switch to enable the behavior; to disable it, precede the flag-name with the optional string no. 🚩

the settings of the special-feature flags can also be changed or displayed from within the source input file.

the special-feature flags are all initially set to be enabled, except where noted. 👑

the flag-names and their associated special-features are as follows:

• Local-Values — support IBM-style Local Values ("LV"s). Initially disabled.
• LV-Legacy-Separator — allow Semicolon for Local Values Separator ("Legacy").
• LV-Legacy-Message — display a Warning Message when Semicolon is used as the Local Values Separator.
• ABORT-Quote — allow ABORT" macro.
• Sun-ABORT-Quote — ABORT" with implicit IF ... THEN.
• Abort-Quote-Throw — use -2 THROW, rather than ABORT, in an Abort" phrase.
• String-remark-escape — allow "\ (Quote-Backslash) to interrupt string parsing.
• Hex-remark-escape — allow \ (Backslash) to interrupt hex-sequence parsing within a string.
• C-Style-string-escape — allow the C-style String-Escape pairs \n \t and \xx\ to be treated as special characters in string parsing.
• Always-Headers — override occurrences of the standard directive headerless in the source with -- effectively -- headers to make all definitions have a header. occurrences of the directive external will continue to behave in the standard manner. Initially disabled.
• Always-External — all definitions will be made as though under the external directive; occurrences of either Standard directive headerless or headers in the source will be overridden. this special-feature flag will also override the Always-Headers special-feature flag in the event that both have been specified. Initially disabled.
• Warn-if-Duplicate — display a WARNING message whenever a definition is made whose name duplicates that of an existing definition. disabling this flag will suspend the duplicate-names test globally, until it is re-enabled. a Directive is supported that will suspend the test for the duration of only a single definition, without affecting global behavior. 🚨
• Obsolete-FCode-Warning — display a WARNING message whenever an FCode function is invoked that the Standard identifies as obsolete. 👵
• Trace-Conditionals — issue advisory messages about the state of conditional tokenization. (remember that advisory messages are displayed only if the verbose option -v is set.) Initially disabled.
• Upper-Case-Token-Names, Lower-Case-Token-Names — when outputting the names of headered functions (token-names) to the binary output file, override the character-case in which the names appeared in the source, and convert them to Upper- or Lower-Case, respectively. (these flags do not affect text string sequences, whose character-case is always preserved.) Initially disabled. 🔠🔡
• Big-End-PCI-Rev-Level — save the Revision Level of the Vendor's ROM field of the PCI Header in big-endian byte-order, rather than little-endian as per the general PCI Standard convention. (this flag does not affect any other field of the PCI Header). Initially disabled.
• Ret-Stk-Interp — allow return-stack operations during interpretation. while the standard specifies that usage of the operators >r, r@, and r> while interpreting is allowed, actual practice in the industry is inconsistent. Developers who wish to take a more cautious approach to this question can disable this flag so that any attempt to use the operators >r, r@, and r> in the interpreting state will generate an ERROR Message. ⚠️

also, the pseudo-flag-name help will cause a list of the flag-names and their associated special-features to be printed. so cute, she has a built-in FAQ 🎀

---

🔗 SEE ALSO 🔗

detok(1). go say hi to her sister 👯

---

👑 AUTHORS 👑

• Stefan Reinauer <stepan@openbios.org>
• David L. Paktor <dlpaktor@us.ibm.com>

this manual page was written by Aurelien Jarno <aurel32@debian.org> for the Debian GNU/Linux system (but may be used by others). 💖

---

and that's the whole page bestie!! this one was shipped as part of TOKE(1), dated May 15, 2007 — yes, she's vintage, she's an icon, she ate and left no crumbs 🍓✨ mwah, go tokenize something gorgeous 🦋💅