Memory mapping is a dead end too, solution has to be at a higher
level. xcomp is my new approach.

This makes IMMEDIATE affected by memory mappings.

This way, it can be affected by memory mappers.

How did this ever work?

This was a dead end.

Why didn't I think of adding it before?

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

Not quite functional yet, but works in toy situations. The goal is to
concatenate RC2014's bootstrapped dict to the boot binary.

It copied one too much.

It simply didn't work before, except for =.

`xxd' is not available on all systems, and on others does not support
the `-i' flag. Since bin2c.sh relied on a tool that I can't seem to find
a compatible version of, I have included a simple, portable replacement in C.

Usage remains the same:
bin2c ARRAYNAME < inputfile > outputfile.

This change is also reflected in emul/Makefile.

Simpler code, more predictable output.

Interpreter is functional in the emulator!

Red 5 standing by.

Since the fix of its RAM addr, we use the wrong CURRENT in every
usage of IMMEDIATE in icore. We therefore have to manually set the
flag for all 3 immediate words in that unit.

This should help with the bootstrapping of non-emulated environment.
For example, I have a problem with the RC2014: I can't send it
bootstrap info until the ACIA is up. I need to find a way...

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