To quote the very first paragraph of the bytecode interpreter section[1]:
> The style of interpretation it uses—walking the AST directly—is good enough for some real-world uses, but leaves a lot to be desired for a general-purpose scripting language.
Sometimes it's useful to teach progressively, using techniques that were used more often and aren't as much anymore, rather than firehosing a low-level bytecode at people.
The parsers in crafting interpreters do not use the visitor pattern. The visitor pattern is used when you already have a tree structure or similar. The parser is what gives you such tree structure, the AST. When you have this structure, you typically use the visitor pattern to process it for semantic analysis, code generation, etc.
Yep that's the one, I have to say it's kinda tempting on one hand, but on the other the Pi 5 is still about 4x slower than this already slow Framework 12 with a GPU that barely qualifies being called that so using it would be pretty painful I imagine.
Nice list. USD (Universal Scene Description) has been renamed to OpenUSD. Part of the motivation was to make it easier to search for. Not all the official docs have been updated yet though.
Another example of 'control flow' is the new behavior graph from Khronos (glTF Interactivity Specification). They did a survey of existing visual programming langauges and are trying to making a standard. It's just been released for public comment: https://www.khronos.org/blog/gltf-interactivity-specificatio...
reply