Execute SNUSP/Tcl: Difference between revisions

 

Historically, the Bloated interpreter was evolved from the Modular interpreter, which in turn was evolved from the Core interpreter.

The interpreter for '''Bloated''' SNUSP is considerably more complex, but most of this complexity is limited to the outer parts of the main loop (plus the change in addressing model for the data store, which becomes an unbounded quarter plane). The principal interesting feature is the use of a dictionary to hold the thread-specific values, together with the use of <tt>dict with</tt> to break these variables temporarily out into global variables for processing. The definition of the READ operation also had to change to become non-blocking so that non-availability of a character would not block other threads. In theory, this could have been done with native OS threads, but then the fairness constraints described in the SNUSP language definition would not have been respected. Thread termination is performed by simply deleting the thread's data from the dictionary of threads.

<br clear=all>

 

# Basic I/O to read the program data and get ready for execution

Move

}

 

 

# Basic I/O to read the program data and get ready for execution

Move

}

 

# Basic I/O to read the program data and get ready for execution

}

}

This prints out a random number of random length:

<pre><nowiki>$!/+++++++++%++++++++++++++++++++++++++++++++++++++++++++++++.!/-\