Linked by Thom Holwerda on Fri 15th Feb 2013 10:40 UTC
Thread beginning with comment 552624
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
...snip...
Obligatory link to the obfuscated c contests:
http://ioccc.org/years.html
Incidentally, I wish these contests would focus more on algorithmic obfuscation rather than source code obfuscation. I am not impressed with code that's unreadable because of shortened variable names and whitespace elimination. The best obfuscated code is code which is still incomprehensible even though it uses proper whitespace conventions and comments
IOCCC is in fact one of those contests. You won't win anything in IOCCC if your code is obvious after running it through indent.
BTW, I think my favourite from this contest is:
http://www.ioccc.org/years.html#1998_banks
christian,
I took a look, I wanted to see if I could recognize the pittsburgh file. It segfaults for me every time and I'm not about to debug it. But I searched for and found this screenshot:
http://blog.aerojockey.com/post/iocccsim
I can definitely recognize the point!





Member since:
2011-01-28
moondevil,

"After a few sessions of off-shore code review, one really stops caring about code quality as long as what was requested works."
With all due respect, -10
I've dealt with too much bad code to write it off as ok as long as it works...
Obligatory link to the obfuscated c contests:
http://ioccc.org/years.html
Incidentally, I wish these contests would focus more on algorithmic obfuscation rather than source code obfuscation. I am not impressed with code that's unreadable because of shortened variable names and whitespace elimination. The best obfuscated code is code which is still incomprehensible even though it uses proper whitespace conventions and comments