<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">For those who’ve missed the introduction to my finl project (which is slowly coming along but has little practical application yet), the half-baked original manifesto is here: <a href="https://www.finl.xyz/2020/10/20/why-finl-a-manifesto/" class="">https://www.finl.xyz/2020/10/20/why-finl-a-manifesto/</a></div><div class=""><br class=""></div><div class="">I’m in the midst of writing the scanner/tokenizer right now and thinking about command arguments. Since I’m eschewing the TeX engine on this, I can treat LaTeX-style commands and all their various arguments as first-class entities. This is a second-draft set of thoughts on command parameters. Each parameter has a format and a type. Formats indicate things like whether it’s a required argument or optional argument, types indicate what’s in the argument (e.g., verbatim text, parsed tokens, math, special types like key-value lists, etc.).</div><div class=""><br class=""></div><div class="">I’d love to get feedback from anyone who cares to delve into my ramblings.</div><div class=""><br class=""></div><div class="">-dh</div></body></html>