There is no reason why they should not be used in single-threaded applications as a powerful means to of obfuscation. In order to preserve its uniqueness as a language, Threaded Intercal does not have any kind of shared data structure for communicating between threads. Many systems have been considered but they all appear too similar to other concurrent languages. Instead Threaded Intercal programs communicate by modifying their shared code base. Extending this to a 16-bit channel is left as an exercise to the reader.
All threads share input and output streams.
For the Turing Text model, there is a single input tape and a single output tape, shared by all threads. Note that this means that the character input or output is given as an offset from the last character read or written by the last thread to do so. Inspired by Kyle Dean. Original standard authored by Malcolm Ryan. This Esoteric Programming Languages Ring site owned by Malcolm Ryan .