Cody Boone Ferguson
009e1b7522
The location of the link is in the About menu under the 'Contacting the IOCCC' and above 'Thanks for the help'. At first I had it at the very bottom, under 'IOCCC markdown guidelines', but it seemed better to have it closer to contacting the IOCCC. This is the same location in the no JavaScript menu (which, for those who do not know or forget, is not a requirement except for some screen sizes). The top level Makefile has a new 'security' rule. Updated make help. Typo fixes in make help. SECURITY.html has had a few updates as well: change the wording of entry code is unsupported (it now says 'ALL CODE IN ALL IOCCC ENTRIES IS UNSUPPORTED!!') and it now links to the mkiocccentry repo and how to report a possible security vulnerability in that repo; as that IS supported - and since there was reference to discussing security concerns is in SECURITY.html - even though the entries will not receive security updates - it seemed a good idea to have a link to report such security issues in the mkiocccentry repo. Perhaps the FAQ needs to be updated for this too.
To build:
make
To use:
./prog
Try:
./try.sh
Judges' remarks:
At this point you might be wondering, WTF?*
-
What The Freak (polite form)
-
What's This For? (you may be wondering)
-
What the Fish (python form)
How is this code obfuscated? Well look again:
less prog.c
more prog.c
Where did those underscores come from? Well RTFS!**
** Read the Freaking Source (polite form) ** Read The Freaking Screen (polite form)
If you are still puzzled, look at prog.c with your favorite text editor.
Author's remarks:
Follow these instructions literally!
cat prog.c
gcc -w -o prog prog.c
./prog
You will do a double take.
Hint 1: Do less prog.c. You will see an emphasized string if your
terminal supports bold.
Hint 2: Do wc -c prog.c. This is very long one-liner.
Hint 3: Open the source with an editor like vim or emacs.