
Nothing I can think of is exactly the same in H3sm as in Forth.  I was
going to list the things that are exactly the same here, but there aren't
enough to list. The difference between a 2-stack machine and a 3-stack
machine is quite systemic. Most things are similar, but have more details
to them about what stacks they use, and things involving Size are global
and persistant in H3sm where thier analogs in Forth are less parametric
upon the overall state. It's rather like going from 2D to 3D, for better
and worse. To some extent though it's the same picture in a different
medium. It's still a relatively succinct machine, and if you have the
outline of the machine visualized reasonably well then things will tend to
work as expected. There's more boundary cases in H3sm, but they're
boundary cases.

H3m's core is factored a bit differently than a Forth. I don't have *, /,
*/, BASE or HERE the the core dictionary. As of this writing there's a
"value", but that's probably going. There are no such thing as variables
in a computer. Everything is a pointer. Accept this, and life gets
simpler.

* is big in C for pytes. * also probably wouldn't be a machine op in a
foreseeable H3m silicon engine. It's not needed to build the core, so I
dropped it. That loses BASE, etc. What does remain in core is sufficient
to write anything else, such as an OS.
