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 all
To use:
./hague 2>/dev/null
# enter some text
Try:
./try.sh
Note that you can run the program without feeding it anything and then type in a
message and line by line it will show the right output. Notice also how certain
characters will print a ?.
Judges' remarks:
Compile this program and feed ASCII text into standard input. This program is known to pass lint on some systems and abort lint on others.
This program was selected for the 1987 t-shirt collection.
Think Morse code when you ponder this program. Note how the use of similar variables can be obfuscating! The author noted that this program implements the international Morse standard. Now for extra credit, what Morse message does the program spell out?
Author's remarks:
No remarks were provided by the author.