mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Format fix 2011/goren/README.md

Browse Source
This commit is contained in:
Cody Boone Ferguson committed 2023-05-02 11:24:40 -07:00
1 parent aaaa74a44c
commit 49ef53fc4a
1 file changed
+12 -10
Download Patch File Download Diff File Expand all files Collapse all files
2011/goren/README.md
+12 -10
View File
@@ -1,7 +1,7 @@
# Most artistic # Most artistic
Uri Goren Uri Goren
<goren.uri@gmail.com> <goren.uri@gmail.com>
## To build: ## To build:
@@ -18,8 +18,8 @@ echo "some text" | ./goren
[Cody Boone Ferguson](/winners.html#Cody_Boone_Ferguson) fixed this for macOS. [Cody Boone Ferguson](/winners.html#Cody_Boone_Ferguson) fixed this for macOS.
Before the fix it segfaulted. It worked fine under linux. After fixing it it was Before the fix it segfaulted. It worked fine under linux. After fixing it it was
noticed that the author stated it does not work for 64-bit so it was then tested noticed that the author stated it does not work for 64-bit so it was then tested
as a 32-bit binary (linux) and 64-bit binary (linux, macOS) and both work. Thank as a 32-bit binary (linux) and 64-bit binary (linux, macOS) and both work. It
you Cody! was fixed by changing some `int`s to `long`s. Thank you Cody!
## Try: ## Try:
@@ -49,8 +49,10 @@ something happens! Why?
## Author's remarks: ## Author's remarks:
This program was written in homage to Rene Magritte's picture "La This program was written in homage to [Rene
trahison des images" (The Treachery of Images). Magritte](http://en.wikipedia.org/wiki/Rene_Magritte)'s picture ["La
trahison des images" (The Treachery of
Images)](https://en.wikipedia.org/wiki/The_Treachery_of_Images).
In order to show my unconditional admiration of this work, I avoided In order to show my unconditional admiration of this work, I avoided
using conditions. using conditions.
@@ -70,14 +72,14 @@ One thing I tried to achieve is condition free programming. Many
have noted that conditions make the code harder to read and understand. have noted that conditions make the code harder to read and understand.
A good example would be: A good example would be:
[Brent Burley's 2004 IOCCC winner](http://www.ioccc.org/years.html#2004_burley) [Brent Burley's 2004 IOCCC winner](/2004/burley/burley.c).
That entry omits conditional statements such as "if" and "while". That entry omits conditional statements such as `if` and `while`.
His achievement in improving clarity by omitting conditions is His achievement in improving clarity by omitting conditions is
impressive, but I think it can be taken further, in two ways. impressive, but I think it can be taken further, in two ways.
First, conditional operators, such as ?:, && and ||, can be thrown First, conditional operators, such as `?:`, `&&` and `||`, can be thrown
away. Second, using setjmp and longjmp, which are unfortunately away. Second, using `setjmp` and `longjmp`, which are unfortunately
not in common use, might make it difficult for a novice programmer not in common use, might make it difficult for a novice programmer
to understand the code without referring to the man page. to understand the code without referring to the man page.