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:
echo "some text" | ./goren
Try:
./try.sh
Judges' remarks:
In the words of René François Ghislain Magritte Magritte:
One may ask the surrealist question:
echo 'If | is just a representation of a pipe, then how can data stuff it?' | ./goren
However if one takes a firm stand and declares:
echo '| is just a representation of a pipe because I say so! So stuff it!' | ./goren
something happens! Why?
Author's remarks:
This program was written in homage to Rene Magritte's picture "La trahison des images" (The Treachery of Images).
In order to show my unconditional admiration of this work, I avoided using conditions.
In this work, Magritte points out that a picture of a pipe is not a pipe. But what IS a pipe? This program tries to provide an answer.
Magritte's test for pipes is:
The famous pipe. How people reproached me for it! And yet, could
you stuff my pipe? No, it's just a representation, is it not?
Accordingly, this program only approves pipes which can be used for stuffing data.
One thing I tried to achieve is condition free programming. Many have noted that conditions make the code harder to read and understand. A good example would be: Brent Burley's winning 2004/burley entry.
That entry omits conditional statements such as if and while.
His achievement in improving clarity by omitting conditions is
impressive, but I think it can be taken further, in two ways.
First, conditional operators, such as ?:, && and ||, can be thrown away.
Second, using setjmp(3) and longjmp(3), which are unfortunately not in
common use, might make it difficult for a novice programmer to understand the
code without referring to the man page.
By removing these, the code is 100% condition free, and every function runs its instructions in perfect order. Naturally, this makes the program flow trivial to understand. This can be verified by disassembling the compiled code and looking for conditional jumps (when compiled with gcc on x86, there are none).
Compatibility:
The program should compile with any C compiler, but was tested mostly with gcc on Linux.
It doesn't support 64 bits (due to integer-pointer casts, and a >>31).
It does work on 64-bit Linux, because all functions are below 4GB.