        I realized that I had not made any instruction for actually storing data to the static variables within modules. I created an 'UPDATE' instruction which updates arbitrary, already-existing.  variables in the 'xprivate' variable table.         However, if static variables in the 'xprivate' variable table have been modified, the whole 'XModule' object needs to be updated. Prior to this update, modules were all read-only and stored in a 'ReaderT' monad called 'Runtime', where as mutable information related to evaluation (registers and the stack) were in a separate 'StateT' monad called 'EvalState'. I have now merged the 'EvalState' and 'Runtime' monads together into a single 'StateT' monad called 'Runtime'. Now changes made to modules at runtime will persist as long as the 'Runtime' data is held in context. 		Finally, I am beginning to create a new monadic interface for building arbitrary data structures.
        I realized that I had not made any instruction for actually storing data to the static variables within modules. I created an 'UPDATE' instruction which updates arbitrary, already-existing.  variables in the 'xprivate' variable table.
        However, if static variables in the 'xprivate' variable table have been modified, the whole 'XModule' object needs to be updated. Prior to this update, modules were all read-only and stored in a 'ReaderT' monad called 'Runtime', where as mutable information related to evaluation (registers and the stack) were in a separate 'StateT' monad called 'EvalState'. I have now merged the 'EvalState' and 'Runtime' monads together into a single 'StateT' monad called 'Runtime'. Now changes made to modules at runtime will persist as long as the 'Runtime' data is held in context.
		Finally, I am beginning to create a new monadic interface for building arbitrary data structures.

printedheart/Dao