Readme1.txt
---: 
Quick Readme file for NB1.

2000-June-23, a Friday, circa 8:22 am.
---:

Okay, NB1 is a quick thingy done in about 3 hours,
the support files gkeys and gui (.cc, .h) were
being used in an overly ambitious project, but they
work perfect here.

---:

files:

autorun.txt
test.txt
manic.txt

there are Nasic Level 1 program files,
they're actually
a) plaintext
b) terminated with "end" 
c) the only valid command is "echo" (and "end", which
means "end of file", not "end of program", as it should)
d) boring and dull. and manic doesn't run in the 
current parser. properly.

other files:

dirvy.txt
nb1keys.txt

The latter provides the symbolic table for the
parser/interpeter/user control deck. In order to
avoid symbol conflicts, it is all one big file
rather than one for a seperate thing, e.g. program
tokens and user control deck tokens are all in one.

This is also due to my simple laziness.

Ideally you'd write subsets of the symbolic table,
and have the program automagically combine them,
but that was the ambitious tool that i never got
far in, or part of it. 

yer more files:

gui.cc
gui.h

The user interface , well, input and output.
(just a CLI, not a Windows or X11 GUI. Uses
iostreams (cin, cout) ).

gkeys.cc
gkeys.h

These libraries manage the symbol table. 
partially. 

nb1.cc

this contains:

main()

the main loop

the interactive "user control deck", or CLI interface

the load routines which are used for 
a) loading Nasic Level 1 files
b) loading S+5 files into "gkeys" instances

All in all, it's fairly cool, not very flashy.

---:

Things to make and do:

"help" command, which was in the original overly 
ambitious tool (known as g8, gmain.cc,and stuff, and
not include here, for shame). 

Help is good but I am lazy and I don't think it's needed. 

That, and I like to see people struggle. (sadistic grin).

No, not really... 

um, more commands. 

the VPU, which is the last in the 2 tier system:

---;
Three Tier System

UCD : User Control Deck, aka the User Interface

VM: Virtual Machine, aka Parser

VPU: Visual Processing Unit, aka Engine

and there's glue code between them, like the
Virtual File System which does the loading of 
the files into the VM at the bidding of the user
via the UCD, and the user's reactions to the VPU's
output (which should be "gee, that's kool!" or
"ooops" or whatever).

There's no VPU yet, but it is coming soon, and will
be revised time and time again. 

---:
Why?

Well... I wanted to do something in a few hours. 

Feedback welcome, this was done especially for 
"format" of the #kode crew, also for Nelish (look 
at me leet file format, blatently copied from sMUD),
and Chip (I have a parser at last!) and, I guess I
should say hello to my friend, family, allies, associates,
and enemies... but I won't cause it's not the same
without a neat scroller (obscure reference to C64 demo
scene... which I was never a part of...).

---:
Parting notes:

"Show us a sign of the end."

"Why? Have you found the beginning, that you seek the end?
The beginning and the end are the same point."

---:
Smink, ploink, and sprong.
---] K31, aka Keinall "Granitor" Caddle
