Will Duquette

Got an opinion about `.tclshrc` (or, more likely, `.moltrc`, or whatever the molt-shell client picks)? I never much used it with `tclsh` myself, so I haven't implemented it.

Added #89 to cover `~/.config/molt/config.tcl`.

Syntactically, Molt is based on the TCL 7.6 version of the language, with a few TCL 8.x additions (dictionaries, the "eq" and "ne" operators, "return" with options, "throw", and like...

Yup. "::" is the namespace operator; and by calling the variable `::env` you're referring to the variable called `env` in the global namespace. But as I say, Molt doesn't have...

That's an excellent idea. I'll read it carefully before I proceed.

If I understand the Jim Tcl design, there's a single dictionary for non-local variable names and a single dictionary for commands; and the names of those variables and commands include...

Note: Molt *does* provide equivalents of all of the **standard** TCL return codes. It's the ability to define arbitrary return codes that's lacking.

Notes: * Rust does not provide "~" expansion by default. * The `shellexpand` crate provides both "~" and environment variable expansion in directory paths, using the `dirs` crate for the...

So happens, I’d already written a note to consider no_std for the Molt core. It’s an obvious application, and I’d like to support it. But I also want to support...

Need to check standard TCL for full semantics, e.g., * What happens if the `env()` variable is unset? * Does the mirroring use variable tracing, or is it some other...