Saves us an (ok) indirection and will save us more soon.

This should allow me to simplify LOAD's exit mechanism on block
end.

My mind is getting forthy.

This allows me to reclaim some RAM I hadn't even noticed I
needlessly monopolise.

Now that this section is so small, I think I can see a possibility
for cross-compiling Collapse OS entirely, which would be great
because we could get rid of the relinker.

That INIT thing is unnecessary.

Makes xcomp.fs units shorter.

TODO: implement X['] so that I can remove those XCURRENT patterns.

Now more low/high layers.

This leaves space for xcomp-core which is growing.

This allows us to move words like ABORT" to xcomp-core, which is
I think the last roadblock before being able to unify all drivers
into a single xcomp layer.

No more low/high

DO and LOOP now only compile words from stable ABI, which make them
suitable for xcomp. This will greatly simplify driver writing and
allow us to mostly avoid the low/high divide in drivers.

LEAVE is still xcomp-incompatible though.

This make us very very tight for "<0x100" limit for literal words.
Hopefully, we won't need more stuff in that area of the binary...

This makes [entry] much simpler. Also, remove unused LITS word.

And refreshed description.

Now I struggle to remember why I ever did things they way I did.
There must have been a reason...

Usage of "LIST" wasn't explicit enough for a complete newcomer. I
hope that with this wording, anyone can figure out how to navigate
blocks and learn the system.

Not yet tried on real hardware, but we should be getting pretty
close...

Yup, it was a deja vu. I remember now.

There's a bug where the first char after a-lock isn't a-modded. I
have troubles figuring it out for now. It feels like deja vu. I
think I had the same problem with asm.

Pushed all words directly interfacing with ports and memory offsets to
low level layers. This saves us the need for keeping those variables in
runtime memory.

The goal is to insert device drivers in between.

That makes it easier to write drivers that can be xcompiled.

In emulator of course...

On the emulator of course...

Gave more priority to CPU in the emulator because initialization would
otherwise be horrendously slow.