IOCCC image by Matt Zucker

The International Obfuscated C Code Contest

2015/muth - Most complete use of CPP

preprocessor Turing engine

Author:

To build:

    make

To use:

    make -B [MACHINE=your_machine.h] [TAPE=your_tape.h] [X=[0|1|2|3|4|5|6|7|8|9]] [V=[0|1|2]] run

Try:

    ./try.sh

Judges’ remarks:

This is something we were fearing all along: that the C preprocessor is Turing-complete even without conditionals and recursive file inclusion as some kind of a rewriting system. Now we have the proof!

Author’s remarks:

Preprocessor Turing Engine

Features

Limitations

If the machine does not halt after M(X) steps, you will see unexpanded macros in the output.

Compiler warnings

If V=1 or V=2 is used, you may see “warning: string length is greater than the length '4095' ISO C99 compilers are required to support”.

Programming

Implementing your own Turing machine is easy. Take a look at the supplied header files for examples.

Tape Symbols

Every symbol used (except _) must be explicitly declared using

    #define sym_SYMBOL(sym, _SYMBOL) sym

Example:

    #define sym_1(sym, _1) sym

Tape

The initial content of the tape must be defined in the tape header using a triple like:

    #define tape ((((,),...l2), l1), c, (r1, (r2..., (,))))

The empty pairs (,) represent the continuations of the tape, filled with underscore symbols (_). They are expanded on demand.

State Machine

All transitions are defined in the machine header using the syntax

    #define CURRENT_SCANNED (WRITE, MOVEMENT, NEXT)

where

There must be a state A defined, which becomes the initial state of the machine.

To halt the machine, use the keyword break as in

    #define A_1 (2, break)

Inventory for 2015/muth

Primary files

Secondary files


Jump to: top