release winning entries of IOCCC28 under the year 2024

Congratulations to:

* 2024/anders - Prize in sound coding - layered music generator
* 2024/burton - Prize in pentagrammatology - wordle hard mode solver
* 2024/cable1 - Prize in bot talk - LLM inference engine
* 2024/cable2 - Prize in murky waters - salmon recipe
* 2024/carlini - Prize in perfect timing - Intel 4004 emulation
* 2024/codemeow - Prize in tray planting - bonsai generator
* 2024/endoh1 - Prize in patient pointillism - slow ray tracer in CPP
* 2024/endoh2 - Prize in solid body physics - rotating rigid body simulation
* 2024/ferguson1 - Prize in diabolical logistics - Oregon trail pact with the devil
* 2024/ferguson2 - Prize in yil-tas - Navajo code talker translator
* 2024/howe - Nice accent eh-ward - mini vi
* 2024/kramer - Prize in linguistic arithmetic - natural language numerical calculator
* 2024/kurdyukov1 - Prize in phased periodicity - phase of the Moon
* 2024/kurdyukov2 - Prize in art restoration - JPEG artifact removal
* 2024/kurdyukov3 - Prize in virtual quietus - gaming VM and doom
* 2024/kurdyukov4 - Prize in embiggening - encode without literals
* 2024/maffiodo - Prize in creative interpretation - Jav\*script interpreter
* 2024/mills - Prize in ℤ₃ - Infocom v3 story interpreter
* 2024/stedolan - Best one liner - icon from MD5
* 2024/straadt - Prize in imitative rebooting - OpenRISC CPU and Linux
* 2024/tmarrec - Prize in cyclonic coding - 3D tornado simulation
* 2024/tompng - Prize in quasi bijection - vortex encryptor decryptor
* 2024/weaver - Sur prize - rickroll

Ran `make update` to perform the above.
 	new file:   2024/burton/.entry.json
This commit is contained in:
Landon Curt Noll committed 2025-08-02 14:43:07 -07:00
1 parent 10512e6c79
commit 09750f8899
443 files changed
+182938 -231

No files matched your search

+105
View File
@@ -0,0 +1,105 @@
## To build:
``` <!---sh-->
make all
```
### Bugs and (Mis)features:
Some terminal applications do not handle all Unicode characters adequately.
On Linux, it is better to enjoy this entry on `gnome-terminal` or an equivalent modern terminal emulator.
## To use:
``` <!---sh-->
./prog
```
## Try:
``` <!---sh-->
./try.sh
```
## Judges' remarks:
We had a few minutes of amazement and fun while figuring that the is
something fishy 🐠 wit the [prog.c source code](%%REPO_URL%%/2024/cable2/prog.c).
Those who follow the philosophy of "_seeing is believing_" are
likely to be "_deceived_" when they try to view the
[prog.c source code](%%REPO_URL%%/2024/cable2/prog.c) in a terminal window:
``` <!---sh-->
cat 2024/cable2/prog.c
```
**HINT**: There is a command line flag to the `cat(1)` tool may provide a clue.
**HINT**: For those who might not be familiar with the
[U"string" literal prefix](https://en.cppreference.com/w/cpp/language/string_literal.html):
When using the U literal prefix, anything inside the quotes is encoded as **UTF-32**.
**HINT TO FUTURE SUBMITTERS**: Now that we have awarded
this **clever entry**, please understand that this
[salmon is now old hat](https://en.wikipedia.org/wiki/Salmon_hat).
What was **murky waters** for **IOCCC28** in 2024 will, in the future,
be immediately seen through when analyzing future submissions to the IOCCC.
In other words, to win a future IOCCC, you will need to do **MORE**
than simply employing this fun obfuscation trick! :-)
## Author's remarks:
Salmon: a most fishy submission
#### About
This program obviously prints the squares of the numbers from 1 to 10. Or does it? The author got a little hungry for char-grilled salmon, and there's clearly something fishy going on with those unused #defines. Or is there? What the actual f*sh is going on here? Follow the three steps below for maximum enjoyment.
**Step 1:**
``` <!---sh-->
cat prog.c
```
**Step 2:**
``` <!---sh-->
make clobber all
```
**Step 3:**
``` <!---sh-->
./prog
```
Scratch head. Then, [slap head with fish](https://www.youtube.com/watch?v=T8XeDvKqI4E).
You may suspect there's something fishy with the `Makefile`, but you would be wrong. It just invokes `cc -o prog prog.c`
You may suspect `cat` might be eating the salmon in step 1 (see `2015/endoh2`), but you would be even wronger. Confirm by looking at the program source using GitHub or `emacs` or `nano`.
You are probably now even more confused, in which case, return to step 1.
<!--
Copyright © 1984-2025 by Landon Curt Noll and Leonid A. Broukhis. All Rights Reserved.
You are free to share and adapt this file under the terms of this license:
Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)
For more information, see:
https://creativecommons.org/licenses/by-sa/4.0/
-->