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 all
There is an alternate version for those with a compiler that support
-traditional-cpp. See Alternate code below.
To use:
./wall
Alternate code:
This version is the original but which can be used if you have a compiler that
supports the -traditional-cpp option.
Alternate build:
make alt
Alternate use:
Use wall.alt as you would wall above.
Judges' remarks:
The original version did not have a ';' character in the first line. This caused a number of System V C pre-preprocessors to gripe about a syntax error.
This program is a masterpiece of obfuscation and humor. Larry Wall (the hacker who gave us rn and patch, etc.) asks you to compile and consider the warning message generated by the C compiler. Then execute the program and type characters into its standard input. You will see why the compiler documents the program.
Author's remarks:
No remarks were provided by the author.