Landon Curt Noll
81b4f460b7
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 commit2955e5d07eand commit2955e5d07e. 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.
Fourth International Obfuscated C Code Contest
View the index.html web page for the given winning entry for information on how
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 1987 suggested even more
categories than in 1986.
Hints for what to do and not to do were also given in the rules.
For example, a simple excessive abuse of /lib/cpp was discouraged unless the
abuse was unusual. The mailboxes for the contest were moved from nsc to amdahl.
The practice of posting a preliminary set of rules for the next year was started
this year.
Rules and results were posted to comp.lang.c and comp.unix.wizards with an announcement in news.announce.important. Micro/Systems Journal published the 1987 winning entries. Mary Ann Horton included a version of the 1987 winning entries in an appendix of her C book Portable C Software International Edition (published under the name Mark R Horton). The first announcement of winning entries at the Summer 87 USENIX was helped by a small fly that danced all over the foils.
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.