Files
ioccc/2005
Cody Boone Ferguson d1a462593f Bug fix and add alt code to 2005/anon
Previously the alt rule in the Makefile defined NO_STTY which stops the
code from using stty(1) at the beginning and at the end. The stty sane
resulted in a bus error in macOS and since the sole purpose was to set
echo back on I changed it to stty echo (which works). (The NO_STTY macro
is still checked, see below.)

Added alt code with vi(m) like movements.

The way to get it to not use stty is to use either make alt-no_stty or
no_stty. The former will compile into anon.alt and the latter will
compile into anon.

Format and typo fix README.md file.
2023-11-20 10:45:10 -08:00
..
2023-11-20 03:43:44 -08:00
2023-11-19 16:00:41 -08:00
2023-05-12 20:10:38 +10:00
2020-12-30 16:57:03 -08:00
2023-10-07 04:35:47 -07:00

2005 marked the "The Eighteenth International Obfuscated C Code Contest"

Standard IOCCC stuff

Look at the README.md file for the given winner for information on how to compile the entry 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.

The IOCCC has a web site and now has a number of international mirrors. The primary site can be found at https://www.ioccc.org/.

Use make(1) to compile entries. It is possible that on non-Unix / non-Linux systems the Makefile needs to be changed. See the Makefile for details.

This year we included most of the information included by the submitters in the README.md files.

Read over the Makefile for compile/build issues. Your system may require certain changes (add or remove a library, add or remove a #define).

Some ANSI C compilers are not quite as good as they should be. If yours is lacking, you may need to compile using gcc instead of your local compiler.

Remarks on some of the entries

We believe you will be impressed with this year's winners.

In particular:

Remarks on some of the losing entries

There were some outstanding entries that did not win. Unfortunately some very good entries lost because they:

  • depended too much on non-portable side effects in expressions; and/or

  • depended too much on a particular byte order; and/or

  • required the use of a special script, data file or pseudo-machine language that was not supplied with the entry.

We hope the authors of some of those entries will fix and resubmit them for the next IOCCC.

Final Comments

Please feel free to send us comments and suggestions about the competition, this README.md or anything else that you would like to see in future contests.

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.

If you have problems with any of the entries, AND YOU HAVE A FIX, please send us the fix please submit your fixes fix as a GitHub pull request.

We will be happy to credit those who submit successful GitHub pull requests in the entry's README.md.

For the latest information on how to contact the IOCCC Judges please visit https://www.ioccc.org/contact.html.

For news of the next contest watch https://www.ioccc.org/.

=-=

Copyright (C) 2005, Landon Curt Noll, Simon Cooper, and Leonid A. Broukhis. All Rights Reserved. Permission for personal, educational or non-profit use is granted provided this copyright and notice are included in its entirety and remains unaltered. All other uses must receive prior permission from the contest judges.