Stories
Slash Boxes
Comments

SoylentNews is people

25th International Obfuscated C Code Contest (2018)

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

canopic jug writes:

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.
25th International Obfuscated C Code Contest (2018) | Log In/Create an Account | Top | 26 comments | Search Discussion
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: 1) by redneckmother on Monday May 07 2018, @06:36PM

    by redneckmother (3597) on Monday May 07 2018, @06:36PM (#676729)

    (See a porting project description below)

    I'm not much of a typist (school of seek and ye shall find), so I employ "search and replace" to improve function / procedure / variable / parameter names... I usually start out with some funky short string as a name, then s/r to a descriptive one. Sheesh, modern editors - who'd a thunk it?

    After much wailing and gnashing of teeth, I converted a coworker to using the same technique - he had been partial to using variable / parameter names like "j1", "j2", etc. for both locals and globals. He also gained appreciation for documentation in comments. Oftentimes, comments explaining intent are helpful for identifying logic and coding errors.

    --
    Mas cerveza por favor.