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
Try:
./roemer
Judges' remarks:
Do you know what this program does? If you do, look again, there is more here than meets the PI.
Author's remarks:
Passes lint, but not with the strictest options, for it contains some
"null-statements", as well as two identifiers which are, if compilers only take 6
characters, the same. It also uses write(2), so not totally system
independent.
You are very much invited to pass this program through a C-beautifier (first
strip newlines and tabs, if your cb can't do that).