Files
ioccc/2006
Cody Boone Ferguson d2bbc264e1 Consistency and other fixes in manifest
As the index.html/README.md files say 'Alternate code' the 'alternative
source' has been changed to 'alternate code'. Similarly the text 'script
to try alternative code' was changed to 'script to try alternate code'.

A mistake was made where something referred to as being the alt code was
not the alt code (or the other way round).

Changed 'alternate alternative code' (or something like that) to 'second
alternate code'. This happened in steps and it might not, now that I
think on it, be the best wording, but this can be addressed later.

Rebuilt html files and .entry.json files.
2024-05-03 08:04:18 -07:00
..
2024-05-01 09:53:30 -07:00
2024-05-01 09:53:30 -07:00
2024-05-01 09:53:30 -07:00
2024-05-01 09:53:30 -07:00
2024-05-01 09:53:30 -07:00
2024-05-01 09:53:30 -07:00
2024-05-01 09:53:30 -07:00
2024-05-01 09:53:30 -07:00
2024-03-20 16:03:01 -07:00
2023-10-07 04:35:47 -07:00

Nineteenth International Obfuscated C Code Contest

Standard IOCCC stuff

View the index.html web page for the given winning entry for information on how on how to compile it and how to run the winning program. Look at the winning source and try to figure how it does what it does! You may then wish to look at the Author's remarks for even more details.

The IOCCC has a web site and now has a number of international mirrors. The primary site can be found at www.ioccc.org.

Use make to compile entries. It is possible that on non-Unix / non-Linux systems the Makefile needs to be changed. See the Makefile for details.

This year we included most of the information included by the submitters in the README.md files (that were used to build the index.html web pages).

Read over the Makefile for compile/build issues. Your system may require certain changes (add or remove a library, add or remove a #define).

Some ANSI C compilers are not quite as good as they should be. If yours is lacking, you may need to compile using gcc instead of your local compiler.

Remarks on some of the entries

There were some outstanding entries that did not win. Unfortunately some very good entries lost because they:

  • depended too much on non-portable side effects in expressions;

  • depended too much on a particular byte order;

  • required the use of a special script, data file or pseudo-machine language that was not supplied with the entry.

We hope the authors of some of those entries will fix and re-submit them for the next IOCCC.

We believe you will be impressed with this year's winning entries. The Best of Show is a fine example of (retro) obfuscation. But don't ignore the other entries! There are games, puzzles, puzzle solvers, simulators, emulators, calculators and graphical and audio tools.

This year a single person won three awards and another two awards! Many authors won for the first time this year. (Please note that judging is done completely anonymously. Be warned that we may disqualify entries that reveal the identity of the submitter).

Final Comments

IMPORTANT NOTE: See contact.html for up to date contact details as well as details on how to provide fixes to any of the entries. See also the IOCCC FAQ for additional information on the IOCCC.