Files
ioccc/1986
Landon Curt Noll 81b4f460b7 require display_as to be a lower case word in .entry.json
The `display_as` field in an `.entry_json` file must match
the regex `^[a-z][0-9a-z]*$` now.  This is needed to reduce
errors during the final round while converting a potential
submission to entry form.

Modify `1992/buzzard.2/.entry.json` and
`1993/rince/.entry.json` to change `display_as` field
to use lower case.

Correct `2012/omoikane/.entry.json` to correctly
reflect changes made by commit 2955e5d07e
and commit 2955e5d07e.

Change `bin/cvt-submission.sh` to verify that the `display_as`
matches the above regex.

Changed `bin/cvt-submission.sh` VERSION from "2.2.2 2025-06-30"
to "2.3.0 2025-07-02".

Rebuild all tarballs, both at the entry and the year level
due recent changes to `var.mk`, `1337.mk`, and `ioccc.css`.

Rebuild sitemap due to the changes above.

Ran `make update` to test and perform the above.
2025-07-02 16:04:33 -07:00
..
2025-01-09 23:11:43 -08:00
2024-07-31 10:44:10 -07:00
2023-02-23 04:42:16 -08:00

Third International Obfuscated C Code Contest

View the index.html web page for the given winning entry for information 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 rules for 1986 suggested categories due to the success of the 1985 judging method. The maximum size was increased from 512 to 1024 bytes. Larry Bassel joined as the second official judge.

A poll was taken for the worst code for BSD and System V program. The Bourne Shell (/bin/sh) won for both systems. The BSD finger program took third place.

Rules and results were posted to net.lang.c and net.unix-wizards. Micro/Systems Journal started regular publishing of the winning entries. The practice of making first announcement of the winning entries at the Summer USENIX BOF (Birds of a Feather) started this year. A notice was posted to net.announce.

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.