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:
./chia
Judges' remarks:
Have you had your morning cup of Java? You might want a second cup before parsing this entry. And give your C pre-processor a triple shot as it tries to handle parameters for "stringification".
Author's remarks:
Two things inspired this entry. First, there were the C programs which were
#define'd to look like Pascal or Visual Basic: the
/bin/sh code from V7
Unix (which reportedly was the
motivation behind this contest!), the VAL
Linker by David Troendle, the
2000/primenum IOCCC entry, ... Looking at these
programs, I thought, "hmm... if it's possible to make C code look like some
weird cross between Pascal, VB, and COBOL, then how about making C code look
like some other language?"
As chance would have it, I was writing some Java code at that time, and one of my net friends was also working on someone else's Java code. We both hated Java; indeed, I hated Java so much that I was tired of hating it. Then I remembered my earlier idea: "Of course! Why not write C code that looks like Java? And poke fun at Java while I'm at it? All ye behold, as I turn anger into action! PH34R MII!!!!!!!" And so, this entry was born. :-)
Besides carrying a revolutionary message in the comments, this entry also draws a spiffy little Koch snowflake fractal on the screen, with the help of ANSI escape sequences.
The code requires a preprocessor that can stomach all kinds of nonsense that are passed as parameters to macros for stringification. GNU cpp handles such things just fine, but certain broken preprocessors may decide to freak out when they see macro parameters that don't look like C tokens.