Files
ioccc/2005
Cody Boone Ferguson 22e483723c Make bug statuses in index.html files quotes
Instead of code blocks the bug / (mis)features statuses are quoted
rather than in a code block. In the case that there is more than one a
line break was added at the end of all but the last one.

A bug status was renamed to be slightly more correct (maybe more than
one was renamed for the same purpose but at least one was).

The bug statuses in the quotes are now bold to let them stand out
better.
2024-07-17 09:54:33 -07:00
..
2024-03-20 16:03:01 -07:00
2024-06-07 02:10:24 -07:00
2023-10-07 04:35:47 -07:00

Eighteenth 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 the entry 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.

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.

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).

The IOCCC has a website and now has a number of international mirrors. The primary website can be found at https://www.ioccc.org/.

Remarks on some of the entries

We believe you will be impressed with this year's winning entries.

In particular:

Remarks on some of the losing 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; and/or

  • depended too much on a particular byte order; and/or

  • 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 resubmit them for the next IOCCC.

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.