Final Concept, number sux.
Interpreting Rules.
Additions to function calling, that make function calling actually
USEFUL! ??
You have to be able to control the current 'this'. This is
achieved through two symbols, that you can place BEFORE any function
name or paramter or ()'s to make the current 'this' move about
within the Tree Xml structure, and to use logic testing on what is
currently 'this'.
so 'THIS' ALWAYS has focus :).
> at any time says 'this' = what was 'this' when interpret function started.
< says that after this function has run, keep what is returned and set it to be 'this'.
'<root' will return the root xml node as this :).
For convenience, all CONTAINERS get and set and del methods have shortcuts that can handle keys of the following forms:
'this' = /Root/User 1) relative short <get aThing <get someData 2) relative long <get aThing/someData 3) absolute whatever <get /Root/User/aThing/someData These are all equivalenet, 'get ..' and 'get .' are like internally a 'parent' and 'this' and 'this' which all just wrap down to either n_This() n_Get >(this) . get (<new String a ./../ <plus >(<name) <plus /./.) for string concatenation you must KEEP the plus's this or the unappended current 'this' will still be 'this'. <root gets you the root.
+environment variables..