Files
ioccc/1984
Landon Curt Noll 9f57052020 rewrite bin/tar-entry.sh
We rewrote the `bin/tar-entry.sh` algorithm so that we do NOT have
to require Linux to produce a compressed tarball that is byte-for-byte
identical to a macOS compressed tarball for the same entry.

Changed `bin/tar-entry.sh` VERSION from "1.2 2024-03-22"
to "1.3 2024-03-25".

Added `bin/untar-entry.sh` to untar an entry from the
compressed tarball.

Added `make untar_entry_tarball` to untar all entry files.

Added `make untar_year_tarball` and `make untar_all_tarball`
stub Makefile rules.  The core it referred to does not yet exist.

Updated IOCCC manifest.  Updated `.entry.json` for `2004/sds`.

Performed `make www` to update web pages.  In most cases the
entry `index.html` added an inventory link for the new `.tar.tstamp` file.

Performed `form_entry_tarball` to complete the test of the above.

TODO: Test the results under Linux.

TODO: Update `bin/tar-year.sh`.  Update year level compressed tarballs.

TODO: Update `bin/tar-all.sh`.  Update top level compressed tarball.

TODO: Write `bin/untar-year.sh` and `bin/untar-all.sh`.
2024-03-25 22:44:34 -07:00
..
2024-03-25 22:44:34 -07:00
2024-03-25 22:44:34 -07:00
2024-03-25 22:44:34 -07:00
2024-03-25 22:44:34 -07:00
2024-03-25 22:44:34 -07:00
…
2024-03-20 16:03:01 -07:00
2024-03-20 00:19:52 -07:00
2024-03-20 00:19:52 -07:00
…

First annual Obfuscated C Code Contest

In 1984, the first contest was held. The name of the contest was simply "First annual 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! This year we only had remarks from two authors but these came years later.

Restrictions against machine dependent code were not in the rules in 1984. The source file size restriction was only 512 bytes. Rules and results were posted to net.lang.c and net.unix-wizards. The contest was announced in a net.lang.c post.

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.