Re:Exploring mullender.c – A deep dive into the first IOCCC ...
by StavrosK on Sunday August 30, 2020 @11:53AM
(#24323632)
The IOCCC can use a UX improvement where they have, for each entry, pages with an introduction, the hints page, how the thing works, the actual code and what happens when you run it (including output).
As it stands, it's very interesting to read but most examples are hard to run and I always end up going away unfulfilled.
Re:Exploring mullender.c – A deep dive into the first IOCCC ...
by LainIwakura on Sunday August 30, 2020 @12:02PM
(#24323691)
This is why I do these write ups, I want to document the most obtuse pieces of code I can and explain the logic in a clear way =) I'll be writing more so be on the look out!
The meaning of "obfuscated C" as the contest requires was not well-defined at that time and had to be amended for a very long time. There are at least 5 more entries that abused and subsequently changed the rules at that time [1] [2] [3] [4] [5]. ([6] is an exception; this kind of abuse of the rules is allowed and now common.)
> [...] if compilers started doing funny things with it, you wouldn't be able to write things like JITs at all.
Well, see [7].
[1] https://www.ioccc.org/1987/biggar/hint.html
[2] https://www.ioccc.org/1988/spinellis.hint
[3] https://www.ioccc.org/1989/jar.1.hint
[4] https://www.ioccc.org/1993/lmfjyh.hint
[5] https://www.ioccc.org/1994/smr.hint
[6] https://www.ioccc.org/1995/spinellis.hint
[7] https://www.ioccc.org/2011/richards/hint.html