Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Monday May 07 2018, @01:44PM   Printer-friendly
from the do-you-see-what-I-did-there? dept.

The International Obfuscated C Code Contest (IOCCC) has now posted the winning entries from its 25th event. The summary of winning entries does NOT contain brief explanations of each winning entry, so you can try to spot the tricks yourself. If you don't mind seeing a brief summary of each entry, there is an alternate page with spoilers linked to from the main page.

The goals of the IOCCC are to write the most Obscure/Obfuscated C program within the contest's rules, while showing the importance of programming style, in an ironic way. It stresses the C compilers with unusual code and illustrates some of the subtleties of the C language. Lastly it provides a safe forum for poor C code.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by jb on Tuesday May 08 2018, @07:26AM

    by jb (338) on Tuesday May 08 2018, @07:26AM (#676936)

    The x86 author was steadfastly opposed to using comments

    I've never understood that attitude.

    Surely assembly language (for any given target architecture) has got to be the language that encourages comments more than any other. After all, isn't that why the instructions are all so short -- so there's room left over for a comment on every line?

    The same held true even back when 40-column displays were a thing -- with 80+ cols to play with, there's really no excuse...

    On the other hand, I feel your pain with deciphering x86 code. That's one instruction set that seems to have been designed to discourage readability (which only makes good comments even more important...).

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2