Files
ioccc/1988
Cody Boone Ferguson 87c74196c1 Fix menu and various other fixes
The menu in all html pages for the FAQ was fixed to link to the step 0
(of how to enter the contest) and also it was renamed ('Enter the
IOCCC').

I also went through the most important sections of the FAQ (how to
enter and the mkiocccentry related questions) and checked the
register.html, pw-change.html and submit.html pages. It is possible I
have missed something but I think it's in pretty good shape nonetheless.
2024-12-27 13:47:34 -08:00
..
2024-12-27 13:47:34 -08:00
2024-12-27 13:47:34 -08:00
2024-12-27 13:47:34 -08:00
2024-12-27 13:47:34 -08:00
2024-12-27 13:47:34 -08:00
2024-12-27 13:47:34 -08:00
2024-12-27 13:47:34 -08:00
2024-03-20 16:03:01 -07:00
2024-12-27 13:47:34 -08:00
2024-08-21 23:42:28 -07:00

Fifth International Obfuscated C Code Contest

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.

The maximum size of entries was raised from 1024 to 1536 bytes, however smaller entries were encouraged. Due to the Best abuse of the rules entry of 1987, a limit of 160 chars in the compile line was introduced.

This year, the Best of Show was given to the most unusual entry and the best abuse of the C Preprocessor rather than the most well rounded entry.

Rules and results were posted to comp.lang.c, comp.sources.unix and alt.sources. The 1988 winning entries will be published in the Micro/Systems Journal.

Winning entries for previous years were repackaged with each year being in its own directory. Makefiles and hints were also provided. The package was posted to the comp.sources.unix newsgroup. They are also available on a wide number of USENET archive sites.

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.