Hello Wes!

12 Jun 03 13:37, you wrote to me:

 >> That _very_ cool! Just to load the configfile require damn mutch..

 WG> That's because nowadays we *use* config files. Back in the day, a
 WG> separate program would be written which handled the configuration.
 WG> Usually, it was a simple BASIC program that you would edit and run. It
 WG> would then emit preference changes as entries in a  jump table which
 WG> was referenced by the assembly code at run time.

Hmm.. there writes a binary configfile? Or self modifying code?

 WG> If you were careful and limited the number of configuration options,
 WG> you could sometimes squeeze the whoe jump table into the zero page --
 WG> the first 256 bytes of memory, excluding those reserved by the kernel
 WG> and the CPU. Doing so meant that your code ran faster (two less cycles
 WG> per load) and would be  smaller (one fewer argument to the opcode).

:-)

Regards, Bo

... It's nice to be important, but it's more important to be nice.

--- Squish/UNIX v1.11