That is it.
That is the whole of iXml.
it is one Xml Node, with a few Native Functions predefined for you,
and ONE interpret function. (+ plus the native calling stuff )
This interpret function is very small (4 a4 pages printed) and
it has been implemented in java 1.1 with a DataHashtable and
AttributeHashtable called Ojet ver 2.
Implemented/refined to c_Ojet.c ver 2, with own xml like structure, and memory management and native functions through reflection/ function pointers in c, and all ansi subset I could do, except persistence although I did do file streams in and out and readLine, readFile and writeLine and so on.. just no proper persistence. Tooo loopy for me to handle in my brain, although I know what I want and it's simple enough for me to ignore at present..
Reimplemented in Java 1.1 on top of nicely modified tiny.xml freeware xml parsing and validating package. EDU-Ware.
Firing a function at a Xml Node made it do some work.
What if this work was to getParentNode() ??
or what if this work was to getChildNode(childname) ??
Then the navigating around the tree would become just more work, and not internal functions anymore. Just more native functions that GIVE IT IT'S FUNCTIONALITY.
You can write any script, and define your script around the data structure, wrapping meaningful function names over more complicated scripting doing the work via more scripts in turn :0.