More testing

I have verified that the double ops get tokenized properly. (<< >> ++ --) and the new ones (// ./ ..) The new double ops are file object expressions (complete file names), although Default intends to expand the use of those operators into sub command namespace classifiers.

xchars loads properly, for example:

Load ./xchars;  // Works fine ( I have not actually tested the semicolon terminator)

That is the Default syntax, so:

MyMacro() {  // Lay out this macro definition
   Load ./xchars;
   Load ../hardly/stacks;
   Load //home/loadables/sqlite;
}

MyMacro();  // Causes the actions above

That will eventually work fine. The default settings on this are not rreconfigurable, and the allowed chars on file names is a distinct set includes the asterisk.  Room to just recompile and try different settings by changing the valid chars.