Landon Curt Noll
f29b37e49a
Prepare for the winners of **IOCCC28**. > However these are not the 2024 droids you are looking for. :-) The HTML menu (both JavaScript and non-JavaScript) has been updated. The `Status -> Rules and guidelines' have been replaced with two separate menus `Status -> IOCCC rules` and `Status -> IOCCC guidelines`. Added a new top level `social.html` page: built from a new `social.md`. Sorted rules for building specific web pages in the top level `Makefile`. Added `make social` to make the `social.html` page from `social.md`. The `bin/gen-top-html.sh` now is able to process a argument of **social** to process the new top level `social.html` page. Changed `bin/gen-top-html.sh` VERSION from "2.0.0 2025-03-13" to "2.0.1 2025-07-25". Below `About -> Home page` a new `About -> IOCCC social media` menu item as added. Because the menu change touched every HTML file, we changed the general copyright date range for HTML files from "1984-2024" to "1984-2025" due to the extensive changes made for **IOCCC28**. Those markdown files that were modified in 2025 had their copyright date range also changed from "1984-2024" to "1984-2025". Rebuilt tarballs and sitemap due to the extensive HTML rebuilding. Ran `make update` to perform the above.
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.