Files
ioccc/2012
Landon Curt Noll f679e76142 processed more of John Dalbec's fix of 2000/dlowe
Added processing of "%%REPO_TOP_URL%%" tokens to `bin/subst.default.sh`.

Updated `find-missing-links.sh` to not falsely report missing links
when a "%%REPO_TOP_URL%%" token is used.

Changed `bin/subst.default.sh` VERSION from "1.3.2 2024-08-05"
to "1.4.0 2025-04-16".

Changed `bin/find-missing-links.sh` VERSION from "1.1.1 2024-04-28"
to "1.2.0 2025-04-16".

Due to a `pandoc(1)` bug fix, `2011/fredriksson/index.html` and
`2012/kang/index.html` were modified.  The bug fix removed extraneous
whitespace that was previously introduced into HTML under certain
situations.  These 2 changes do **NOT** impact the way web browsers
render these pages, however.

Updated sitemap.

Updated tarballs based on entry mods since 2025 March 4
(commit 233e5e90a5 just prior
to the IOCCC28 open).

Tested the above via `make update` on macOS.
2025-04-16 13:54:27 -07:00
..
…
…
2024-06-07 02:10:24 -07:00
2025-03-01 10:32:08 -08:00
2024-08-21 23:42:28 -07:00
2025-03-01 10:32:08 -08:00
…

Twenty First 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.

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.

Historical note:

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

Historical update:

The IOCCC website once had a number of international mirrors. As of 2020 Dec 29, GitHub serves as the distributed server farm for the IOCCC winner repo that GitHub renders as Official IOCCC website - www.ioccc.org.

Remarks on some of the entries

We believe you will be impressed with this year's winning entries. We had a very difficult time picking a single best from among the other entries because the overall quality of the submissions were so high.

This year we selected the top 4 entries for particularly high honors:

But don't ignore the other winning entries! There are games, utilities, eye candy, calculators and graphical tools to explore.

This year, Yusuke Endoh won with two entries, one of which (endoh1) won the special Honorable mention award. Eight of the winning entries were from people who won in previous years.

This year we had a number of authors from Asia. We saw our second entry from China and our first from Korea. We are pleased to see outstanding entries from areas of the world that have not been active in past contests. Will we see an upswing of entries from South America, Africa and Antarctica next year? :-)

Please note that judging is done completely anonymously. Please do NOT reveal your identity in your source code. In the future we may disqualify entries that reveal the identity of the submitter!

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

  • would take years to execute

  • were way way oversize and didn't even attempt to justify their excess by a clever abuse of the rules

  • obfuscate themselves by simply invoking a complex state machine

  • depend on a single obfuscation trick

  • could only be run on a particular vendor's platform

  • were very similar to previous winning entries

  • were based on an overused theme such as yet another fractal display program

  • didn't work as documented

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

There is a risk in submitting an entry that is similar to a well used theme by previous winning entries. Previous entries set a very high bar. A new winning entry must not only compete against other submissions form the current year, they must also excel over similar winning entry in some particularly impressive way.

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.