22nd International Obfuscated C Code Contest Starts Thursday 1 Aug 2013

achowe writes "The 22nd International Obfuscated C Code Contest opens 2013-Aug-01 03:14:15 UTC through to 2013-Oct-03 09:26:53 UTC. The rules have been updated, in particular Rule 2 (size rule) has changed. The draft rules and guidelines are available online. In addition there is now an IOCCC Size Rule Tool to aid with counting the secondary size rule. Questions and comments for the Judges can be emailed to q.2013@ioccc.org and must include 'IOCCC 2013' in the subject. Or contact them via Twitter @IOCCC." Anyone planning on entering?

Comments

Re:You want obfuscated code?

[TheCarp]

While I agree perl can be written readable, and I do try to do that whenever I am writting perl... it also has so much syntactic sugar and idiom that writing obfuscated perl is a bit too easy.

I used to give people a perl code test that included the line:

"split //;"

Where else can you operate on one variable, save your result in another, and specify neither? Never mind functions that operate differently depending on whether or not they are called in scalar context.

Re:A contest to code poorly?

[achowe]

IOCCC 1991 Best Utility was a vi like editor in 1536 bytes; Debian went on to use the unobfuscated version "ae" as a small editor for the rescue floppy for many many years.

Obscure dates/times, too

[Anonymous Coward]

2013-Aug-01 03:14:15 UTC through to 2013-Oct-03 09:26:53

Umm, where'd those dates/times come from?

03:14:15 looks like pi truncated to 4 decimal places, but why Aug 1? And where'd the close date/time come from?

Re:Obscure dates/times, too

[Anonymous Coward]

pi = 3.1415 92653 589...
That explains the close time anyway, I didn't look at the dates.

And this is for people who

[azav]

think that C isn't obfuscated enough.