Files
ioccc/2005
Cody Boone Ferguson 33aaf98d23 Restore anonymous locations to anonymous authors
In the case of 1984, 2001 and 2005 the anonymous authors had location
codes but the country code for anonymous locations is XX. This has been
done and the authors.html, location.html and the respective index.html
files have been rebuilt.

One file was not touched because I was not sure how to best approach it
as an email was provided and possibly other things too (in particular a
second author of 2015/endoh1).
2024-05-06 09:27:04 -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

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.

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

Use make(1) 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

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.