Landon Curt Noll
dbf6921b3a
Updated 1337 hacker rulz to version 7. Added `1337.mk` to contain the updated 1337 hacker rulz (v7). We use an optional include of `1337.mk` (or `../1337.mk`, or `../../1337.mk`) to include the 1337 hacker rulz. Changed `make deep_magic` to `make more_magic`. Changed `bin/tar-entry.sh` VERSION from "1.3.7 2024-07-22" to "1.3.8 2024-07-23". Changed `bin/tar-year.sh` VERSION from "1.2.5 2024-07-22" to "1.2.6 2024-07-23". Add `make new_entry` to `YYYY/Makefile` and `template/Makefile.year`. Change `make new_year` to use `sort -n -u`. Made minor debug message fixes to `bin/new-year.sh`. Changed `bin/new-year.sh` VERSION from "1.3 2024-07-23" to "1.3.1 2024-07-23". Improved `bin/add-dir.sh` to update `YYYY/Makefile` with the new entry directory name. Changed `bin/add-dir.sh` VERSION from "1.0 2024-07-21" to "1.1 2024-07-23". Performed `make www` to accomplish the above and to test under macOS.
Twenty Sixth International Obfuscated C Code Contest
Standard IOCCC stuff
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.
Some C compilers are not quite as good as they should be. If yours is lacking, you may need to compile using clang or gcc instead of your local compiler.
The primary website can be found at www.ioccc.org.
Remarks on some of the winning entries
This year's winning entries are impressive!
The Most in need of debugging - 2019/endoh is very inventive in a way it produces its own text!
The Most alphabetic- 2019/ciura has an amazing vocabulary!
There are again nods to entries of the years:
These nods to not run afoul of the guideline:
We tend to dislike programs that: ... are rather similar to previous entries
because the entry 2019/dogon appropriately pays homage to past entries without blatantly reusing their code.
...We'll stop spouting too many details now. Have fun exploring all the entries!
Remarks on some of submissions that did not win
Some entries tried to get around the size limit by submitting a data file that was really C code and then blindly including code in prog.c.
Quite a few entries suffered from undefined behavior like accessing uninitialized locals and/or reading-writing below the stack. We advise running your entry through valgrind to make sure those mistakes are avoided.
Using extra arguments to main, or arguments of wrong types as a quick and dirty
way of declaring variables is now passé. Clang, for example, rejects them outright.
We hope the authors of some of those entries will fix and re-submit them for the next IOCCC.
Some entries seemed to have a good idea, but the implementation of the idea was limited in scope.
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.