SquirrelBox 1.6 alpha 5.99 changes & updates

[Dan Cook]

(why did I not just go to "alpha 6"; it's not like it would be 1.7!)

This update is to reflect the MANY changes that I make as I edit the
tutorials and reshape things to make way for other optimizations.
Though nothing fundamental about the CORE language has changed, these
changes are more than enough to impact the validity of any source file
and the coding of more include files.

I WILL press the button and put the other ops back in, but I just
wanted to save my place and catch any bugs or issues here before
moving on (verification would be nice?). Here is the list of changes
as I can recall them:

* The tutorials are changing a LOT; I have given a piece of them so
far (what I have)

* The very nature & setup of the include files has changed a LOT. Give
them a look if you have set paradigms on the old ones. The biggest
change is the placement of functions over macros and the renaming of
such ... do we even need the macros anymore?

* I framed some MUCH better number printing functions and some nice
input functions. Slight changes must be made if you want them to work
BEFORE I add back in && and ||, but they are tight!

* No more "this" arguments; that will soon not be much of an
efficiency

* the #endheader directive blocks further #header's from being added

* the #error directive throws errors (used in case of obvious misuse
of includes or w/e)

* No more limitations on where function calls can be used. This is
resolved by pushing all "busy" registers onto the stack before the
call, and popping them back after (that's a MAX of pushPops). On a
side note, that makes passing values more efficient because the A and
HL registers are used with no questions asked.

* The assembly output is captured into a command-prompt looking tab.
That and all assembly output now has happy random colors to the text

* I fixed a bug that make "pass-by-reference" values work backwards :-
S

* I REMOVED the #asminc directive. It seemed convenient, but that
pulls #includes out of the headers where they belong and is only a
MINOR convenience. It is therefore once again possible to #include
the same asm file twice and make your assembler angry. Code those
include files smartly!!