the unbound variable checker now lets you know what top level
assignment the unbound variable occurs in
what is probably a non-working version of compile
compile totally worked, thanks be to God!

top level assignments must be defined before they can be used
(although in some cases it might still work ... top level assignment
being assigned the result of a top level assignment not defined will break
and top level being assigned application using top level assignment
not yet defined will break)
Not sure I want to fix that.  Seems like I probably have to change
my compilation strategy to something more practical (top level
are address or something).  Will handle in later revision, I'm sure.
cleaned up example file

finished the project by pulling all the elements together
in the untyped_assign.lua

There's probably some issues that won't get fixed until
the next revision.