For those who would undertake the challenge of designing a UTM exactly as Turing specified see the article by Davies in . Davies corrects the errors in the original and shows what a sample run would look like. He successfully ran a (somewhat simplified) simulation. The following example is taken from . For more about this example, see
Turing machine examples. Turing used seven symbols { A, C, D, R, L, N, ; } to encode each 5-tuple; as described in the article
Turing machine, his 5-tuples are only of types N1, N2, and N3. The number of each "configuration" (instruction, state) is represented by "D" followed by a unary string of A's, e.g. "q3" = DAAA. In a similar manner, he encodes the symbols blank as "D", the symbol "0" as "DC", the symbol "1" as DCC, etc. The symbols "R", "L", and "N" remain as is. After encoding each 5-tuple is then "assembled" into a string in order as shown in the following table: Finally, the codes for all four 5-tuples are strung together into a code started by ";" and separated by ";" i.e.: This code he placed on alternate squares—the "F-squares" – leaving the "E-squares" (those liable to erasure) empty. The final assembly of the code on the tape for the U-machine consists of placing two special symbols ("e") one after the other, then the code separated out on alternate squares, and lastly the double-colon symbol "
::" (blanks shown here with "." for clarity): The U-machine's action-table (state-transition table) is responsible for decoding the symbols. Turing's action table keeps track of its place with markers "u", "v", "x", "y", "z" by placing them in "E-squares" to the right of "the marked symbol" – for example, to mark the current instruction
z is placed to the right of ";"
x is keeping the place with respect to the current "mconfiguration" DAA. The U-machine's action table will shuttle these symbols around (erasing them and placing them in different locations) as the computation progresses: Turing's action-table for his U-machine is very involved.
Roger Penrose provides examples of ways to encode instructions for the universal machine using only binary symbols { 0, 1 }, or { blank, mark | }. Penrose goes further and writes out his entire U-machine code. He asserts that it truly is a U-machine code, an enormous number that spans almost 2 full pages of 1's and 0's. Asperti and Ricciotti described a multi-tape UTM defined by composing elementary machines with very simple semantics, rather than explicitly giving its full action table. This approach was sufficiently modular to allow them to formally prove the correctness of the machine in the
Matita proof assistant. ==See also==