There are many situations where it can be useful. Worth it.

I'm planning on adding other subfolders. 8086 for example...

There's no reason to run them only under CVM.

The idea is to consider assemblers as "runtime" apps instead of
placing them in the "bootstrap" section of the blocks. These apps
will be used for much more than bootstrapping.

Moved its documentation to doc/asm.txt and made its code blocks
more compact.

With the Visual Editor, BROWSE is of dubious value. Even before that,
it was of dubious value. It's the only user of the CASE word, which
is also of dubious value: too complicated for its own good.

The CMD pattern used in VE is much better.

ref #97

The SD card driver is a bit too slow to be bearable. I'll write
_crc16 in z80 and see how it goes.

Less noisy this way

And fix broken negative display in ".".

Why did I ever think that using CM was a good idea? any comparison
with numbers more than 0x8000 apart would be wrong...

To update LATEST offset more easily. Will be useful for recipes.

There is an alternate git history where I continued the Forth-ification of
words, including "SKIP?", but that was a bad idea: because that word was
written by flow control immediates, I stepped into quicksands where stability
became necessary in z80c.fs and I couldn't gracefully get out of it.

I'm stepping back and take this opportunity to replace the shoddy SKIP? algo
with a more straightforward (?br) implementation.

(br) and (?br) will always stay in boot code where it's easier manage a stable
ABI.

Modest first step

A bug in rdWS made zasm error out when omiting its 3rd argument.

fixes #90

I had forgotten about that ordering thing: depending on the platform
cfspack doesn't read files in a directory in the same order.

This allows us to get rid of the zasm.sh wrapper.