Cody Boone Ferguson
03694c587d
At least one link in the FAQ was fixed (not to a file but a named reference). The FAQ has not been checked entirely for broken links because the changes have got a bit out of hand and an entire make www will have to be performed due to a problem I discovered doing the below. Other improvements were made. When going through the FAQ for broken links another problem was discovered, one that broke the scripts that rely on jstrdecode(1). These have been fixed but need further testing with make www. Some index.html files were modified; for why this can be done without make quick_readme2index see below on what changed and why it could be done this way. When going through the FAQ for broken links I discovered some issues with some entries' synopsis. This means that a number of index.html and .entry.json files have been updated. The reason the index.html files could be modified without running the scripts which would were broken due to the jstrdecode(1) issue (a missing option in the scripts) is because I used sgit(1). However, a single README.md file was modified and the index.html file was not modified just yet. That will happen with make www. The change is not significant, however, so this should be okay this time. As the next step is a long process I therefore decided to commit these things to get them out of the way to try and prevent the commit from being even larger. Minor fixes in next/try.sh and next/try.alt.sh were also discovered when going through the FAQ. Minor typos were made in the FAQ. The .gitignore file was also updated: with the last change I accidentally made it so vim swap files without a filename are not ignored. That means there have to be two vim swap file globs.
Eleventh International Obfuscated C Code Contest
View the index.html web page for the given winning entry for information on how
on how to compile it and how to run the winning program.
Look at the winning source and try to figure how it does what it does!
You may then wish to look at the Author's remarks for even more details.
Name and address information are separated from the actual program prior to judging. This eliminates any chance that we would bias our judging for/against any person or group.
This year we retracted the guideline that discouraged the use of C
constructs such as 3["curds"]. At one time, certain ANSI compilers did
not consider such expressions to be valid ANSI C. Alert readers noted
that the current ANSI standard considered them to be valid. We were
unable to find an ANSI C compiler that flagged such expressions as
errors.
Rule abuse was encouraged this year - two of this year's winning entries found new and interesting abuses of the rules. Next year's rules will change due to these (smr and dodsond2) entries' forms of abuse.
Want to be an IOCCC Judge?
We are thinking about adding a 3rd judge to our team. A 3rd judge would help distribute the work load as well as to allowing us to possibly expand or reshape the contest.
The ideal 3rd judge would have all of the following:
- thorough knowledge of the C language (ANSI and K&R)
- thorough knowledge of common C libs (libc, libm, curses, ...)
- reasonable written communication skills (able to write
README.mdfiles, for example) - appreciation for well-written non-obfuscated code
- willing to devote ~4 weekend days in January (starting Jan 96) for judging
- located in the San Francisco (California, US) Bay Area, or able to travel (paying your own way) to the SF Bay Area during judging, or able to link to the other IOCCC judges by some form of a video link
Any of the following, though not required, would be a plus:
- familiar with portability issues
- some
/bin/shexperience - some Perl experience
- some C++ experience
- some experience with low-level X11 programming
- attends USENIX conferences on a regular basis
- good sense of humor
- loves chocolate and other fine foods :-)
If you think this may be you, send an email before 31 Dec 1995, to:
judges@toad.com (use the Subject: 3rd judge)
Include in your message:
- Your name, address, email address and phone number
- Why would you want to be an IOCCC judge?
- How well do you match each of the above qualifications?
- What special skills would you bring to the team?
If you have any questions about the above, feel free to ask us via email at the above address.
Looking for an IOCCC WWW site
We would like to setup an IOCCC home page somewhere out in WWW land. If you have a well known stable site that would be willing to give us access to put up some IOCCC html pages, please send an email (say prior to 31 Dec 1995) to:
judges@toad.com (use the Subject: www site)
describing your site and any other appropriate comments. Thanks!
A few notes regarding future contests
Due to changes in the USENIX conference calendar, the 1995 contest will be delayed. Because there will be no Summer 1995 USENIX conference, the 1995 IOCCC entries will be announced at the Jan 1996 USENIX conference.
The 1995 contest will not open until late October 1995, and will close sometime around the end of December 1995. The rules for the 1995 contest have not been formed at this time and are not expected to be ready for distribution until late October 1995.
Be sure to wait until the 1995 rules are posted before submitting entries. Rules differ from year to year, sometimes in significant ways.
Please send us comments and suggestions what we have expressed above. Also include anything else that you would like to see in future contests. See How to contact the IOCCC for how to provide us with your comments and suggestions today.
For those who appreciate a bit of Internet history, this is how people used to contact the IOCCC in this given year, via Unix to Unix CoPy (UUCP):
...!{sun,pacbell,uunet,pyramid}!hoptoad!judges
judges@toad.com
If you use, distribute or publish these entries in some way, please drop us a line. We enjoy seeing who, where and how the contest is used, as well as details on how to provide fixes to any of the entries.
Final Comments
IMPORTANT NOTE: The email addresses found above are for historical purposes only, and should not be used today. See contact.html for up to date contact details as well as details on how to provide fixes to any of the entries. See also the IOCCC FAQ for additional information on the IOCCC.
Credits
We would like to thank Barbara Frezza for her role as official chef of the contest. Landon Curt Noll and Larry Bassel appreciated the opportunity to serve as official taste testers. And as usual, the food was excellent. The official menu of the 1994 Obfuscated C Contest dinner:
Antipasto: meats, cheeses, olives, peppers, pickles, artichokes
Soup: Cream of tomato
Salad: spring mix
Pasta: Linguine with wild mushrooms and Reggiano Parmesan
Seafood: Salmon in cream sauce or lobster claws
Vegetable: Zucchini
Dessert: Homemade chocolate/pecan brownies, fruit