Files
ioccc/1987
Cody Boone Ferguson e257cd1af0 Add 1987/wall/try.sh
This script automates through a pipeline some of the input suggested in
the README.md. The README.md still has some of what try.sh has because
it shows that you can do it entering line by line.
2024-01-05 09:09:34 -08:00
..
2024-01-05 06:32:37 -08:00
2024-01-05 06:43:39 -08:00
2024-01-05 08:36:14 -08:00
2024-01-05 09:09:34 -08:00
2023-12-26 09:00:03 -08:00

1987 marked the "The Fourth International Obfuscated C Code Contest"

Look at the README.md file 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 1997 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 winners. Mark R. Horton included a version of the 1987 winners in an appendix of his C book Portable C Software International Edition. The first announcement of winners 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 addition information on the IOCCC.

Copyright and License

Copyright (c) 1987,2023, Landon Curt Noll and Larry Bassel. All Rights Reserved. This work is licensed under a Creative Commons CC BY-SA 4.0 DEED Attribution-ShareAlike 4.0 International license. If you do use this work in some form, the IOCCC judges would appreciate (but does not require) if you were to send us a note about your use.