diff --git a/1984/README b/1984/README index a3877917c..f0277d631 100644 --- a/1984/README +++ b/1984/README @@ -1,10 +1,18 @@ In 1984, the first contest was held. The name of the contest was simply ``Obfuscated C Code Contest''. + +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments for even more details. + Restrictions against machine dependent code were not in the rules in 1984. The source file size restriction was only 512 bytes. Rules and results were posted to net.lang.c and net.unix-wizards. +=-= + Copyright (c) 1984, Landon Curt Noll. All Rights Reserved. Permission for personal, educational or non-profit use is granted provided this this copyright and notice are included in its entirety diff --git a/1985/README b/1985/README index 586b3376b..237056b75 100644 --- a/1985/README +++ b/1985/README @@ -1,4 +1,10 @@ -185 marked the second year of the Obfuscated C Code Contest. +1985 marked the second year of the Obfuscated C Code Contest. + + +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments for even more details. Hints against machine dependent code were added to the rules to avoid another 1984 style winner. Rules and results were posted to net.lang.c @@ -6,6 +12,8 @@ and net.unix-wizards. Larry Bassel was invited to help in the judging. Awards were given to 5 classes of programs since we were unable to select only the best 4. +=-= + Copyright (c) 1985, Landon Curt Noll & Larry Bassel. All Rights Reserved. Permission for personal, educational or non-profit use is granted provided this this copyright and notice are included in its entirety diff --git a/1986/README b/1986/README index 25a232ac4..59b1d7005 100644 --- a/1986/README +++ b/1986/README @@ -1,20 +1,28 @@ The 1986 contest was named: "The Third International Obfuscated C Code Contest" -Copyright (c) 1986, Landon Curt Noll & Larry Bassel. -All Rights Reserved. Permission for personal, educational or non-profit use is -granted provided this this copyright and notice are included in its entirety -and remains unaltered. All other uses must receive prior permission in writing -from both Landon Curt Noll and Larry Bassel. + +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments for even more details. The rules for 1986 suggested categories due to the success of the 1985 judging method. The maximum size was increased from 512 to 1024 bytes. Larry Bassel joined as the second official judge. A poll was taken for the worst code for BSD and System V program. -The Bourne Shell (/bin/sh) won for both systems. The BSD finger +The Bourne Shell (/bin/sh) won for both systems. The BSD finger program took third place. Rules and results were posted to net.lang.c and net.unix-wizards. Micro/Systems Journal published started regular publishing of the winners. The practice of making first announcement of the winners at the Summer Usenix BOF started this year. A notice was posted to net.announce. + +=-= + +Copyright (c) 1986, Landon Curt Noll & Larry Bassel. +All Rights Reserved. Permission for personal, educational or non-profit use is +granted provided this this copyright and notice are included in its entirety +and remains unaltered. All other uses must receive prior permission in writing +from both Landon Curt Noll and Larry Bassel. diff --git a/1987/README b/1987/README index 672af5387..bca360a5f 100644 --- a/1987/README +++ b/1987/README @@ -1,10 +1,10 @@ 1987 marked the "The Fourth International Obfuscated C Code Contest" -Copyright (c) 1987, Landon Curt Noll & Larry Bassel. -All Rights Reserved. Permission for personal, educational or non-profit use is -granted provided this this copyright and notice are included in its entirety -and remains unaltered. All other uses must receive prior permission in writing -from both Landon Curt Noll and Larry Bassel. + +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments for even more details. The rules for 1987 suggested even more categories than in 1986. Hints for what to do and not to do were also given in the rules. For @@ -19,3 +19,11 @@ published the 1987 winners. Mark Horton included a version of the 1987 winners in an appendix of his C book. The first announcement of winners at the Summer 87 Usenix was helped by a small fly that danced all over the foils. + +=-= + +Copyright (c) 1987, Landon Curt Noll & Larry Bassel. +All Rights Reserved. Permission for personal, educational or non-profit use is +granted provided this this copyright and notice are included in its entirety +and remains unaltered. All other uses must receive prior permission in writing +from both Landon Curt Noll and Larry Bassel. diff --git a/1988/README b/1988/README index 06a6287b7..53e9bd4eb 100644 --- a/1988/README +++ b/1988/README @@ -1,10 +1,10 @@ 1988 marked the "The Fifth International Obfuscated C Code Contest" -Copyright (c) 1988, Landon Curt Noll & Larry Bassel. -All Rights Reserved. Permission for personal, educational or non-profit use is -granted provided this this copyright and notice are included in its entirety -and remains unaltered. All other uses must receive prior permission in writing -from both Landon Curt Noll and Larry Bassel. + +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments for even more details. The maximum size of entries was raised from 1024 to 1536 bytes, however smaller entries were encouraged. Due to the "Best Abuse of the Rules" @@ -14,10 +14,18 @@ This year, the Grand Prize was given to the most unusual entry and best abuse of the C Preprocessor rather than the most well rounded entry. Rules and results were posted to comp.lang.c, comp.sources.unix and -alt.sources. The 1988 winners will be published in the Micro/Systems -Journal. +alt.sources. The 1988 winners will be published in the Micro/Systems +Journal. Winning entries for previous years were repackaged with each year being in its own directory. Make files and hints were also provided. The package was posted to the: comp.sources.unix newsgroup. They are also available on a wide number of Usenet archive sites. + +=-= + +Copyright (c) 1988, Landon Curt Noll & Larry Bassel. +All Rights Reserved. Permission for personal, educational or non-profit use is +granted provided this this copyright and notice are included in its entirety +and remains unaltered. All other uses must receive prior permission in writing +from both Landon Curt Noll and Larry Bassel. diff --git a/1989/README b/1989/README index d71136be8..a300b75b1 100644 --- a/1989/README +++ b/1989/README @@ -1,16 +1,14 @@ 1989 marked the "The Sixth International Obfuscated C Code Contest" -Copyright (c) 1989, Landon Curt Noll & Larry Bassel. -All Rights Reserved. Permission for personal, educational or non-profit use is -granted provided this this copyright and notice are included in its entirety -and remains unaltered. All other uses must receive prior permission in writing -from both Landon Curt Noll and Larry Bassel. + +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments for even more details. Instructions for use: Run make to compile entries (it is possible that on System V or non-unix systems the makefile needs to be -changed). Look at the source and try to figure out what the programs -do, and run them with various inputs. If you want to, look at the -hints files for (minor) spoilers. +changed). This year, the Grand Prize was given to the most useful program. @@ -18,8 +16,7 @@ The "Strangest abuse of the rules" award was given this year to stress the fact that starting in 1990, compiling entries must result an executable regular file. -In two other cases, we included System V portable versions of winning -programs. The makefile always uses the portable version of the "Best +The makefile always uses the portable version of the "Best self modifying program" because there as no loss of functionality in using it. In the case of the "Best game" winner, however, some functionality is lost in the portable version and so the makefile uses @@ -30,3 +27,11 @@ Rules and results were posted to comp.lang.c, comp.sources.unix, and alt.sources. They have been made available on a wide number of Usenet archive sites such as uunet. The 1989 winners will be published in the Micro/Systems Journal. + +=-= + +Copyright (c) 1989, Landon Curt Noll & Larry Bassel. +All Rights Reserved. Permission for personal, educational or non-profit use is +granted provided this this copyright and notice are included in its entirety +and remains unaltered. All other uses must receive prior permission in writing +from both Landon Curt Noll and Larry Bassel. diff --git a/1990/README b/1990/README index 1cf585dd9..43bf87136 100644 --- a/1990/README +++ b/1990/README @@ -1,18 +1,10 @@ 1990 marked the "The Seventh International Obfuscated C Code Contest" -Copyright (c) 1990, Landon Curt Noll & Larry Bassel. -All Rights Reserved. Permission for personal, educational or non-profit use is -granted provided this this copyright and notice are included in its entirety -and remains unaltered. All other uses must receive prior permission in writing -from both Landon Curt Noll and Larry Bassel. -Instructions for use: Run make to compile entries (it is possible that -on System V or non-unix systems the makefile needs to be changed). The -ansi.mk may need to be changed if your ANSI C compiler is not gcc. - -Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -(minor) spoilers. +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments for even more details. This year, the Grand Prize won a standing ovation at USENIX. @@ -31,3 +23,11 @@ some of the contest entries were appreciated. Rules and results were posted to comp.lang.c, comp.sources.unix, and alt.sources. They have been made available on a wide number of Usenet archive sites such as uunet. + +=-= + +Copyright (c) 1990, Landon Curt Noll & Larry Bassel. +All Rights Reserved. Permission for personal, educational or non-profit use is +granted provided this this copyright and notice are included in its entirety +and remains unaltered. All other uses must receive prior permission in writing +from both Landon Curt Noll and Larry Bassel. diff --git a/1991/README b/1991/README index df2d624c4..62732a4cd 100644 --- a/1991/README +++ b/1991/README @@ -1,20 +1,16 @@ 1991 marked the "The Eighth International Obfuscated C Code Contest" -Copyright (c) 1991, Landon Curt Noll & Larry Bassel. -All Rights Reserved. Permission for personal, educational or non-profit use is -granted provided this this copyright and notice are included in its entirety -and remains unaltered. All other uses must receive prior permission in writing -from both Landon Curt Noll and Larry Bassel. + +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments for even more details. Instructions for use: Run make to compile entries. It is possible that on BSD or non-unix systems the makefile needs to be changed. -Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -(minor) spoilers. - This year, we did not single out an entry that was better than all of -the rest. We selected 3 entries that were, in our opinion, went beyond +the rest. We selected 3 entries that were, in our opinion, went beyond all of the other entries this year: Grand Prize by Brian Westley @@ -47,17 +43,17 @@ reject entries of this type. However we provided more portable versions so that more people could compile these programs. This year we received entries that made use of the X Window System. -This functionality is now available on many systems, we feel that -programs that use these are now portable enough to be valid entries. +This functionality is now available on many systems, we feel that +programs that use these are now portable enough to be valid entries. -We may allow programs to make use of the X Window System libs and include -files, provided that they can operate with a system running at the level +We may allow programs to make use of the X Window System libs and include +files, provided that they can operate with a system running at the level of at least X11r4. Requiring the use of imake, a specific window manager, -specific display hardware, or a specific user interface (Openl**k, -M*tif, ...) is likely not to be allowed. We will provide a more detailed +specific display hardware, or a specific user interface (Openl**k, +M*tif, ...) is likely not to be allowed. We will provide a more detailed explanation of our viewpoint in next year's rules. -In order to encourage more 'normal' looking C programs, we are considering +In order to encourage more 'normal' looking C programs, we are considering the following change to the maximum size rule: Your source, not counting any , , and a character, @@ -70,7 +66,7 @@ is not likely to happen soon. We are waiting until c++ compilers become common place on a wide number of systems. We also need time to brace ourselves for what obfuscation c++ could wield! -Be sure to wait until the 1992 rules are posted before submitting entries. +Be sure to wait until the 1992 rules are posted before submitting entries. We may fine tune the rules to reflect the some ideas above. Please send us comments and suggestions what we have expressed above. @@ -83,6 +79,14 @@ Send such email to: Credits: -We would like to thank Barbara Frezza for her role as official chef +We would like to thank Barbara Frezza for her role as official chef of the contest. Landon Noll appreciated the opportunity to serve as assistant pizza chef. Larry Bassel was official taste tester. Yummo! + +=-= + +Copyright (c) 1991, Landon Curt Noll & Larry Bassel. +All Rights Reserved. Permission for personal, educational or non-profit use is +granted provided this this copyright and notice are included in its entirety +and remains unaltered. All other uses must receive prior permission in writing +from both Landon Curt Noll and Larry Bassel. diff --git a/1992/README b/1992/README index 75236b4bf..0c3c35a5a 100644 --- a/1992/README +++ b/1992/README @@ -1,24 +1,19 @@ 1992 marked the "The Ninth International Obfuscated C Code Contest" -Copyright (c) 1992, Landon Curt Noll & Larry Bassel. -All Rights Reserved. Permission for personal, educational or non-profit use is -granted provided this this copyright and notice are included in its entirety -and remains unaltered. All other uses must receive prior permission in writing -from both Landon Curt Noll and Larry Bassel. + +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments for even more details. Use make to compile entries. It is possible that on BSD or non-unix systems the makefile needs to be changed. See the Makefile for details. -Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitters. - Read over the makefile for compile/build issues. Your system may require certain changes (add or remove a library, add or remove a #define). A number of compilers had problems optimizing certain entries. Some compilers do optimize, but the resulting program -does not work. By default we have left off -O from compile lines. +does not work. By default we have left off -O from compile lines. You might want to add -O back, or add it back for certain entries where performance is important. @@ -30,9 +25,9 @@ years. The new size rules size probably contributed to the overall high quality. FYI: By tradition, we do not record the count the number entries, - nor do we give our our guess as to the number of entries - received. For folks who wonder, we can say that we consumed - about 2000 pages of output (printing between 2 and 4 normal + nor do we give our our guess as to the number of entries + received. For folks who wonder, we can say that we consumed + about 2000 pages of output (printing between 2 and 4 normal pages per side) during the judging process this year. The new instructions for submitting entries worked well - we were @@ -57,14 +52,14 @@ deserving entries. These categories have not been eliminated. We will likely be awarding them in future years. We received a few entries whose instructions were rot13'd. While -nothing was said about this in the rules, we found that it made the +nothing was said about this in the rules, we found that it made the judging process a little harder, so we may request that this not be done this in the future. Some thought has been given to a separate obfuscated perl contest. Watch comp.lang.perl for details! -Be sure to wait until the 1993 rules are posted before submitting entries. +Be sure to wait until the 1993 rules are posted before submitting entries. We may fine tune the rules to reflect the some ideas above. Please send us comments and suggestions what we have expressed above. @@ -86,3 +81,11 @@ Credits: We would like to thank Barbara Frezza for her role as official chef of the contest. Landon Noll and Larry Bassel appreciated the opportunity to serve as official taste testers. Yummo! + +=-= + +Copyright (c) 1992, Landon Curt Noll & Larry Bassel. +All Rights Reserved. Permission for personal, educational or non-profit use is +granted provided this this copyright and notice are included in its entirety +and remains unaltered. All other uses must receive prior permission in writing +from both Landon Curt Noll and Larry Bassel. diff --git a/1993/README b/1993/README index eabacfc33..d2806ca62 100644 --- a/1993/README +++ b/1993/README @@ -1,19 +1,14 @@ 1993 marked the "The Tenth International Obfuscated C Code Contest" -Copyright (c) 1993, Landon Curt Noll & Larry Bassel. -All Rights Reserved. Permission for personal, educational or non-profit use is -granted provided this this copyright and notice are included in its entirety -and remains unaltered. All other uses must receive prior permission in writing -from both Landon Curt Noll and Larry Bassel. + +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments for even more details. Use make to compile entries. It is possible that on BSD or non-unix systems the makefile needs to be changed. See the Makefile for details. -Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitters. - Read over the makefile for compile/build issues. Your system may require certain changes (add or remove a library, add or remove a #define). @@ -29,7 +24,7 @@ not be able to compile the winners, sorry! A few notes regarding future contests: -Be sure to wait until the 1994 rules are posted before submitting entries. +Be sure to wait until the 1994 rules are posted before submitting entries. Rules differ from year to year, sometimes in significant ways. In 1994, we will retract the guideline that discouraged the use of C @@ -54,6 +49,14 @@ email the fix (patch file or the entire changed file) to the above address. Credits: -We would like to thank Barbara Frezza for her role as official chef +We would like to thank Barbara Frezza for her role as official chef of the contest. Landon Noll and Larry Bassel appreciated the opportunity to serve as official taste testers. And as usual, the food was excellent. + +=-= + +Copyright (c) 1993, Landon Curt Noll & Larry Bassel. +All Rights Reserved. Permission for personal, educational or non-profit use is +granted provided this this copyright and notice are included in its entirety +and remains unaltered. All other uses must receive prior permission in writing +from both Landon Curt Noll and Larry Bassel. diff --git a/1994/README b/1994/README index b97a2f3ad..a09e18efc 100644 --- a/1994/README +++ b/1994/README @@ -1,20 +1,14 @@ 1994 marked the "The Eleventh International Obfuscated C Code Contest" -Copyright (c) 1994, Landon Curt Noll & Larry Bassel. -All Rights Reserved. Permission for personal, educational or non-profit use is -granted provided this this copyright and notice are included in its entirety -and remains unaltered. All other uses must receive prior permission in writing -from both Landon Curt Noll and Larry Bassel. +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments for even more details. Use make to compile entries. It is possible that on BSD or non-unix systems the makefile needs to be changed. See the Makefile for details. -Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitters. - Read over the makefile for compile/build issues. Your system may require certain changes (add or remove a library, add or remove a #define). @@ -98,13 +92,13 @@ 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 winners 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. +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. @@ -124,7 +118,7 @@ email the fix (patch file or the entire changed file) to the above address. Credits ------- -We would like to thank Barbara Frezza for her role as official chef +We would like to thank Barbara Frezza for her role as official chef of the contest. Landon 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: @@ -136,3 +130,11 @@ Pasta: Linguine with wild mushrooms and Reggiano Parmesan Seafood: Salmon in cream sauce or lobster claws Vegetable: Zucchini Dessert: Homemade chocolate/pecan brownies, fruit + +=-= + +Copyright (c) 1994, Landon Curt Noll & Larry Bassel. +All Rights Reserved. Permission for personal, educational or non-profit use is +granted provided this this copyright and notice are included in its entirety +and remains unaltered. All other uses must receive prior permission in writing +from both Landon Curt Noll and Larry Bassel. diff --git a/1995/README b/1995/README index c50ee2e74..eca897864 100644 --- a/1995/README +++ b/1995/README @@ -1,11 +1,10 @@ 1995 marked the "The Twelfth International Obfuscated C Code Contest" -Copyright (c) 1996, Landon Curt Noll, Larry Bassel & Sriram Srinivasan. -All Rights Reserved. Permission for personal, educational or non-profit use is -granted provided this this copyright and notice are included in its entirety -and remains unaltered. All other uses must receive prior permission in writing -from Landon Curt Noll, Larry Bassel and Sriram Srinivasan. +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments for even more details. The IOCCC has an official home page: @@ -17,11 +16,6 @@ announcements and much more. Use make to compile entries. It is possible that on BSD or non-unix systems the makefile needs to be changed. See the Makefile for details. -Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitters. - Read over the makefile for compile/build issues. Your system may require certain changes (add or remove a library, add or remove a #define). @@ -30,7 +24,7 @@ This year Sriram Srinivasan joined the judging. The moderator of comp.unix.wizards did not feel that the IOCCC was "wizardly" enough to be posted to comp.unix.wizards - we will no longer post the -winners to this newsgroup - we'll let you the reader decide for yourself the +winners to this newsgroup - we'll let you the reader decide for yourself the wizardlyness of these entries. This year there were several people who won more than once @@ -55,7 +49,7 @@ close sometime around the end of December 1996. The rules for the 1996 contest have not been formed at this time and are not expected to be ready for distribution until late September 1996. -Be sure to wait until the 1996 rules are posted before submitting entries. +Be sure to wait until the 1996 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. @@ -85,7 +79,7 @@ Session One: Antipasti: Crudites, olive selection, pickles, cheese selection Soup: Homemade mushroom and green onion soup -Salad: artichoke, red bell peppers, Italian onions, cucumbers +Salad: artichoke, red bell peppers, Italian onions, cucumbers and Greek olives with mustard vinaigrette Main Course: Pizzas, with a variety of toppings Dessert: Chocolate torte @@ -97,11 +91,11 @@ Salad: Mixed greens with vinaigrette Main Course: Spaghetti with tomato sauce containing mushrooms and black olives selection of hot and mild Italian sausages Bread: Fresh French bread -Dessert: Cookie selection, featuring chocolate chocolate chip cookies and +Dessert: Cookie selection, featuring chocolate chocolate chip cookies and chocolate butter cookies -Session Three +Session Three Antipasti: Crudites, olive selection Salad: Mixed greens with mustard vinaigrette @@ -131,7 +125,7 @@ Dessert: Flourless chocolate torte Session Six: -Antipasti: Carrot and celery sticks with cheese spread, olive selection, +Antipasti: Carrot and celery sticks with cheese spread, olive selection, pickles Bread: Focaccia with black olives and mozzarella cheeses Salad: Mixed spring greens with flowers and mustard vinaigrette @@ -140,3 +134,10 @@ Main Course: Cracked dungeness crab with lemon mayonnaise, broccoli, mixture of white and brown rice Dessert: Key lime pie +=-= + +Copyright (c) 1996, Landon Curt Noll, Larry Bassel & Sriram Srinivasan. +All Rights Reserved. Permission for personal, educational or non-profit use is +granted provided this this copyright and notice are included in its entirety +and remains unaltered. All other uses must receive prior permission in writing +from Landon Curt Noll, Larry Bassel and Sriram Srinivasan. diff --git a/1996/README b/1996/README index 176e434c4..6ed0a8e0d 100644 --- a/1996/README +++ b/1996/README @@ -1,15 +1,14 @@ 1996 marked the "The Thirteenth International Obfuscated C Code Contest" -Copyright (c) 1997, Landon Curt Noll & Sriram Srinivasan. -All Rights Reserved. Permission for personal, educational or non-profit use is -granted provided this this copyright and notice are included in its entirety -and remains unaltered. All other uses must receive prior permission in writing -from Landon Curt Noll and Sriram Srinivasan. - Standard IOCCC stuff -------------------- +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments for even more details. + The IOCCC has an official home page: http://www.ioccc.org @@ -20,11 +19,6 @@ announcements and much more. Use make to compile entries. It is possible that on BSD or non-unix systems the makefile needs to be changed. See the Makefile for details. -Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitters. - Read over the makefile for compile/build issues. Your system may require certain changes (add or remove a library, add or remove a #define). @@ -56,7 +50,7 @@ Remarks on some of the entries This year, Jens Schweikhardt won 3 times ... a new IOCCC record. Meanwhile, Brian Westley came up with his 8th winning entry, twice the number of the next highest count. But with people like Schweikhardt -around, this lead could fall fast. +around, this lead could fall fast. As we state in the guidelines, the names of the winners are as much news to us as they are to you because we keep authorship separate from @@ -75,13 +69,13 @@ There is no 1997 contest. The next contest will not open until sometime in March 1998, and will close sometime around the end of May 1998. The rules for the 1998 contest have not been formed at this time and are not expected to be -ready for distribution until late February 1998. +ready for distribution until late February 1998. -So what happened to 1997? Well the next USENIX Technical Conference +So what happened to 1997? Well the next USENIX Technical Conference will be held Jun 15-19, 1998 (in New Orleans, USA). The 18 month span between conferences will cause the IOCCC to skip over 1997. -Be sure to wait until the 1998 rules are posted before submitting entries. +Be sure to wait until the 1998 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. @@ -95,3 +89,11 @@ 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 email the fix (patch file or the entire changed file) to the above address. + +=-= + +Copyright (c) 1997, Landon Curt Noll & Sriram Srinivasan. +All Rights Reserved. Permission for personal, educational or non-profit use is +granted provided this this copyright and notice are included in its entirety +and remains unaltered. All other uses must receive prior permission in writing +from Landon Curt Noll and Sriram Srinivasan. diff --git a/1998/README b/1998/README index 173e3380f..903bbd5ed 100644 --- a/1998/README +++ b/1998/README @@ -1,16 +1,14 @@ 1998 marked the "The Fourteenth International Obfuscated C Code Contest" -Copyright (c) Landon Curt Noll, Jeremy Horn, Peter Seebach -and Leonid A. Broukhis, 1999. -All Rights Reserved. Permission for personal, educational or non-profit -use is granted provided this this copyright and notice are included in its -entirety and remains unaltered. All other uses must receive prior permission -from the contest judges. - Standard IOCCC stuff -------------------- +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments for even more details. + The IOCCC has its own domain. The IOCCC has an official home page is now: http://www.ioccc.org @@ -18,11 +16,6 @@ The IOCCC has its own domain. The IOCCC has an official home page is now: Use make to compile entries. It is possible that on BSD or non-unix systems the makefile needs to be changed. See the Makefile for details. -Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitters. - Read over the makefile for compile/build issues. Your system may require certain changes (add or remove a library, add or remove a #define). @@ -131,3 +124,12 @@ The next IOCCC is planned to start towards the end of 1999. Watch: http://www.ioccc.org for news of the next contest. + +=-= + +Copyright (c) Landon Curt Noll, Jeremy Horn, Peter Seebach +and Leonid A. Broukhis, 1999. +All Rights Reserved. Permission for personal, educational or non-profit +use is granted provided this this copyright and notice are included in its +entirety and remains unaltered. All other uses must receive prior permission +from the contest judges. diff --git a/2000/README b/2000/README index 702335db2..26e23d859 100644 --- a/2000/README +++ b/2000/README @@ -1,23 +1,16 @@ 2000 marked the "The Fifteenth International Obfuscated C Code Contest" -Copyright (C) Landon Curt Noll, Simon Cooper, Peter Seebach -and Leonid A. Broukhis, 2000. -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. - Standard IOCCC stuff -------------------- -Use make to compile entries. It is possible that on non-Un*x / non-Linux -systems the makefile needs to be changed. See the Makefile for details. +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments for even more details. -Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitters. +Use make to compile entries. It is possible that on non-Un\*x / non-Linux +systems the makefile needs to be changed. See the Makefile for details. Read over the makefile for compile/build issues. Your system may require certain changes (add or remove a library, add or remove a @@ -118,3 +111,11 @@ p.s. The has been mentioned in an Amici Curiae for the DeCSS case. See: and seach on the word ioccc (twice). +=-= + +Copyright (C) Landon Curt Noll, Simon Cooper, Peter Seebach +and Leonid A. Broukhis, 2000. +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. diff --git a/2001/README b/2001/README index 2f6429da5..47b5e500b 100644 --- a/2001/README +++ b/2001/README @@ -1,29 +1,22 @@ 2001 marked the "The Sixteenth International Obfuscated C Code Contest" -Copyright (C) Landon Curt Noll, Simon Cooper, Peter Seebach -and Leonid A. Broukhis, 2001-2002. -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. - Standard IOCCC stuff -------------------- +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments 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, http://www.ioccc.org -Use make to compile entries. It is possible that on non-Un*x / non-Linux +Use make to compile entries. It is possible that on non-Un\*x / non-Linux systems the makefile needs to be changed. See the Makefile for details. -Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitters. - Read over the makefile for compile/build issues. Your system may require certain changes (add or remove a library, add or remove a #define). @@ -95,3 +88,10 @@ Watch: for news of the next contest. =-= + +Copyright (C) Landon Curt Noll, Simon Cooper, Peter Seebach +and Leonid A. Broukhis, 2001-2002. +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. diff --git a/2004/README b/2004/README index 562eb110b..c9e4631dd 100644 --- a/2004/README +++ b/2004/README @@ -1,28 +1,22 @@ 2004 marked the "The Seventeenth International Obfuscated C Code Contest" -Copyright (C) 2001-2004, Landon Curt Noll, Simon Cooper, Peter Seebach -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. - Standard IOCCC stuff -------------------- +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments 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, http://www.ioccc.org/ -Use make to compile entries. It is possible that on non-Un*x / non-Linux +Use make to compile entries. It is possible that on non-Un\*x / non-Linux systems the makefile needs to be changed. See the Makefile for details. -Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitters. - Read over the makefile for compile/build issues. Your system may require certain changes (add or remove a library, add or remove a #define). @@ -84,3 +78,11 @@ Watch: http://www.ioccc.org/ for news of the next contest. + +=-= + +Copyright (C) 2001-2004, Landon Curt Noll, Simon Cooper, Peter Seebach +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. diff --git a/2005/README.md b/2005/README.md index 8f0c32a58..2075ff9a9 100644 --- a/2005/README.md +++ b/2005/README.md @@ -1,28 +1,25 @@ 2005 marked the "The Eighteenth International Obfuscated C Code Contest" ======================================================================== -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. - Standard IOCCC stuff -------------------- +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments 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, > -Use make to compile entries. It is possible that on `non-Un*x` / non-Linux +Use make to compile entries. It is possible that on non-Un\*x / non-Linux systems the makefile needs to be changed. See the Makefile for details. -Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitters. +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). @@ -108,3 +105,10 @@ For news of the next contest watch: > +=-= + +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. diff --git a/2006/README.md b/2006/README.md index 5e7be9c8a..fbdff35b0 100644 --- a/2006/README.md +++ b/2006/README.md @@ -1,28 +1,25 @@ 2006 marked the "The Nineteenth International Obfuscated C Code Contest" ======================================================================== -Copyright (C) 2006, 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. - Standard IOCCC stuff -------------------- +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments 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, > -Use make to compile entries. It is possible that on non-Un*x / non-Linux +Use make to compile entries. It is possible that on non-Un\*x / non-Linux systems the makefile needs to be changed. See the Makefile for details. -Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitters. +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). @@ -79,3 +76,10 @@ For news of the next contest watch: > +=-= + +Copyright (C) 2006, 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. diff --git a/2011/README.md b/2011/README.md index 71847b7e4..7d67a986a 100644 --- a/2011/README.md +++ b/2011/README.md @@ -1,28 +1,25 @@ 2011 marked the "The Twentieth International Obfuscated C Code Contest" ======================================================================== -Copyright (C) 2012, 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. - Standard IOCCC stuff -------------------- +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments 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, > -Use make to compile entries. It is possible that on non-Un*x / non-Linux +Use make to compile entries. It is possible that on non-Un\*x / non-Linux systems the makefile needs to be changed. See the Makefile for details. -Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitters. +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). @@ -77,3 +74,10 @@ For news of the next contest watch: > +=-= + +Copyright (C) 2012, 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. diff --git a/2012/README.html b/2012/README.html deleted file mode 100644 index 5d4aeefc7..000000000 --- a/2012/README.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - - - README - - -

2012 marked the “The Twenty First International Obfuscated C Code Contest”

- -

Copyright © 2012, 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.

- -

Standard IOCCC stuff

- -

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

Use make to compile entries. It is possible that on non-Un*x / non-Linux -systems the makefile needs to be changed. See the Makefile for details.

- -

Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitter.

- -

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. We had -a very difficult time picking a single best from among the other winners -because the overall quality of the winners were so high.

- -

This year we selected the top 4 entries for particularly high honors:

- -
    -

  • Gold award - Balanced use of obfuscation

    - -

    A very extremely subtle and twisted piece of source code! -Even if you start with the zeitak_deobfucate.c source, -you will still have a very challenging time to understand it!

    • -

  • Silver award - Most elementary use of C

    - -

    A fun program that could also have won “Best abuse of -Ghostscript” because it managed to create some PDF files -that Ghostscript could not read.

    • -

  • Bronze award - Best use of cocoa

    - -

    A picture within a picture is worth more than a -thousand (4 byte) words. :-)

    • -

  • Honorable mention - Most complex ASCII fluid

    - -

    When you see this program in action, you too will -very likely say wow as we did!

    • -
- - -

But don’t ignore the other winners! There are games, utilities, -eye candy, calculators and graphical tools to explore.

- -

This year, Yusuke Endoh won with two entries, one of which (endoh1) -won the special Honorable mention award. Eight of the winning entries -were from people who won in previous years.

- -

This year we had a number of winners from Asia. We saw our second -winner from China and first from Korea. We are pleased to see -outstanding entries from areas of the world that have not been -active in past contests. Will we see an upswing of entries -from South America, Africa and Antarctica next year? :-)

- -

Please note that judging is done completely anonymously. Please -do NOT reveal your identity in your source code. In the future we -may disqualify entries that reveal the identity of the submitter!

- -

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

- -
    -

  • would take years to execute

    • -

  • were way way oversize and didn’t even attempt to justify their -excess by a clever abuse of the rules

    • -

  • obfuscate themselves by simply invoking a complex -state machine

    • -

  • depend on a single obfuscation trick

    • -

  • could only be run on a particular vendor’s platform

    • -

  • were very similar to previous winners

    • -

  • were based on an overused theme such as yet another -fractal display program

    • -

  • didn’t work as documented

    • -
- - -

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

- -

There is a risk in submitting an entry that is similar to a well -used theme by previous winners. Previous winners set a very high -bar. A new winner must not only compete against other submissions -form the current year, they must also excel over similar winners -in some particularly impressive way.

- -

Final Comments

- -

Please feel free to send us comments and suggestions about the -competition, this README 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 (patch file or the entire changed file).

- - - - - -
Creative Commons License

© Copyright 1984-2012, -Leo Broukhis, Simon Cooper, Landon Curt Noll -- All rights reserved
-This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

 
- - diff --git a/2012/README.md b/2012/README.md index a4d44b4e6..d46f6b60f 100644 --- a/2012/README.md +++ b/2012/README.md @@ -1,16 +1,15 @@ 2012 marked the "The Twenty First International Obfuscated C Code Contest" ======================================================================== -Copyright (C) 2012, 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. - Standard IOCCC stuff -------------------- +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments 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, @@ -19,11 +18,6 @@ The primary site can be found at, Use make to compile entries. It is possible that on non-Un\*x / non-Linux systems the makefile needs to be changed. See the Makefile for details. -Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitter. - Read over the makefile for compile/build issues. Your system may require certain changes (add or remove a library, add or remove a #define). @@ -132,12 +126,10 @@ For news of the next contest watch: > +=-= --------------------------------------------------------------------------------- - +Copyright (C) 2012, 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. diff --git a/2013/README.html b/2013/README.html deleted file mode 100644 index ceb51c8a1..000000000 --- a/2013/README.html +++ /dev/null @@ -1,121 +0,0 @@ - - - - - - - README - - -

2013 marked the “The Twenty Second International Obfuscated C Code Contest”

- -

Copyright © 2013, 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.

- -

Standard IOCCC stuff

- -

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

Use make to compile entries. It is possible that on non-Un*x / non-Linux -systems the makefile needs to be changed. See the Makefile for details.

- -

Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitter.

- -

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 again be impressed with this year’s winners.

- -

This year, several 8 people won 9 people won 15 awards. For the -first time in the history of the contest, one person, Yusuke Endoh, -won 4 times while Adrian Cable won 3 times! It is also worth noting -that Chris Mills previous win was in 1993. Welcome back Chris!

- -

We, the judges, were very surprised by this as many of the multiple -winners submitted very different styles of entries.

- -

This year was the first time the IOCCC size tool was used. Entries -had to print a value 2053 or less when the -i flag was used.

- -

Several people discovered an undocumented feature in that -certain comments such as:

- -
///*
-
- -

or:

- -
*\
-/
-
- -

were not correctly parsed by the tool. The guidelines stated:

- -
In cases where the above summary and the algorithm implemented by
-the IOCCC size tool source code conflict, the algorithm implemented
-by the IOCCC size tool source code is preferred by the judges.
-
- -

so this abuse was allowed (and encouraged). The judges hope that -the IOCCC size tool author will patch the tool to block this kind -of size abuse in future contests.

- -

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

- -
    -

  • were way way oversize and didn’t even attempt to justify their -excess by a clever abuse of the rules

    • -

  • depend on a single obfuscation trick

    • -

  • could only be run on a particular vendor’s platform

    • -

  • were very similar to previous winners

    • -

  • didn’t work as documented

    • -
- - -

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

- -

There is a risk in submitting an entry that is similar to a well -used theme by previous winners. Previous winners set a very high -bar. A new winner must not only compete against other submissions -from the current year, they must also excel over similar winners -in some particularly impressive way.

- -

Final Comments

- -

Please feel free to send us comments and suggestions about the -competition, this README 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 (patch file or the entire changed file).

- - - - - -
Creative Commons License

© Copyright 1984-2013, -Leo Broukhis, Simon Cooper, Landon Curt Noll -- All rights reserved
-This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

 
- - diff --git a/2013/README.md b/2013/README.md index 4b6958532..d9f58198b 100644 --- a/2013/README.md +++ b/2013/README.md @@ -1,16 +1,15 @@ 2013 marked the "The Twenty Second International Obfuscated C Code Contest" =========================================================================== -Copyright (C) 2013, 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. - Standard IOCCC stuff -------------------- +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments 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, @@ -19,11 +18,6 @@ The primary site can be found at, Use make to compile entries. It is possible that on non-Un\*x / non-Linux systems the makefile needs to be changed. See the Makefile for details. -Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitter. - Read over the makefile for compile/build issues. Your system may require certain changes (add or remove a library, add or remove a #define). @@ -35,7 +29,7 @@ local compiler. Remarks on some of the entries ------------------------------ -We believe you will again be impressed with this year's winners. +We believe you will again be impressed with this year's winners. This year, several 8 people won 9 people won 15 awards. For the first time in the history of the contest, one person, Yusuke Endoh, @@ -112,12 +106,10 @@ For news of the next contest watch: > +=-= --------------------------------------------------------------------------------- - +Copyright (C) 2013, 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. diff --git a/2019/README.html b/2019/README.html deleted file mode 100644 index 127395ce4..000000000 --- a/2019/README.html +++ /dev/null @@ -1,105 +0,0 @@ - - - - - - README - - -

2016 marked the “The Twenty Sixth International Obfuscated C Code Contest”

- -

Copyright © 2019, 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.

- -

Standard IOCCC stuff

- -The primary site can be found at www.ioccc.org. - -

Use make to compile entries. It is possible that on non-Un*x / non-Linux -systems the makefile needs to be changed. See the Makefile for details.

- -

Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitter.

- -

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 C compilers are not quite as good as they should be. If yours is -lacking, you may need to compile using clang or gcc instead of your local -compiler.

- -

Remarks on some of the winners

- -

This year’s winners are impressive!

- -

The “Most in need of debugging” (endoh) is very inventive in a way it produces its own text!

- -

The “Most likely to be awarded” (ciura) has an amazing vocabulary!

- -

There are again nods to winners of the years:

- -
[1991/davidguy](http://ioccc.org/years.html#1991_davidguy)
-[2011/blakely](http://ioccc.org/years.html#2011_blakely)
-
- -

These nods to not run afoul of the guideline:

- -
We tend to dislike programs that:
-...
-are rather similar to previous winners
-
- -

because the entry (dogon) appropriately pays homage to past winners -without blatantly reusing their code.

- -

…We’ll stop spouting spoilers now. Have fun exploring all the entries!

- -

Remarks on some of submissions that did not win

- -

Some entries tried to get around the size limit by submitting a data -file that was really C code and then blindly including code in prog.c.

- -

Quite a few entries suffered from undefined behavior like accessing -uninitialized locals and/or reading-writing below the stack. -We advise running your entry through valgrind to make sure those mistakes -are avoided.

- -

Using extra arguments to main, or arguments of wrong types as a quick and dirty -way of declaring variables is now passé. Clang, for example, rejects them outright.

- -

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

- -

Some entries seemed to have a good idea, but the implementation of -the idea was limited in scope.

- -

Final Comments

- -

Please feel free to send us comments and suggestions about the -competition, this README 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 (patch file or the entire changed file).

- - - - - -
Creative Commons License

© Copyright 1984-2019, -Leo Broukhis, Simon Cooper, Landon Curt Noll -- All rights reserved
-This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.

 
- - diff --git a/2019/README.md b/2019/README.md index a6713d37d..d5175b1a6 100644 --- a/2019/README.md +++ b/2019/README.md @@ -1,16 +1,15 @@ 2016 marked the "The Twenty Sixth International Obfuscated C Code Contest" ========================================================================== -Copyright (C) 2019, 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. - Standard IOCCC stuff -------------------- +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments for even more details. + The primary IOCCC web site can be found at, > @@ -18,11 +17,6 @@ The primary IOCCC web site can be found at, Use make to compile entries. It is possible that on non-Un\*x / non-Linux systems the makefile needs to be changed. See the Makefile for details. -Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitter. - Read over the makefile for compile/build issues. Your system may require certain changes (add or remove a library, add or remove a #define). @@ -64,7 +58,7 @@ Some entries tried to get around the size limit by submitting a data file that was really C code and then blindly including code in prog.c. Quite a few entries suffered from undefined behavior like accessing -uninitialized locals and/or reading-writing below the stack. +uninitialized locals and/or reading-writing below the stack. We advise running your entry through valgrind to make sure those mistakes are avoided. @@ -99,11 +93,10 @@ For news of the next contest watch: > --------------------------------------------------------------------------------- - +Copyright (C) 2019, 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. diff --git a/2020/README.md b/2020/README.md index e5d85bf7d..c1f471e82 100644 --- a/2020/README.md +++ b/2020/README.md @@ -1,14 +1,13 @@ ## 2020 marked the "The Twenty Seventh International Obfuscated C Code Contest" -Copyright (C) 2020, 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. - ## Standard IOCCC stuff +Look at the README.md file for the given winner for information +on how to compile the winner 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 comments for even more details. + The primary IOCCC web site can be found at, > @@ -16,11 +15,6 @@ The primary IOCCC web site can be found at, Use make to compile entries. It is possible that on non-Un\*x / non-Linux systems the makefile needs to be changed. See the Makefile for details. -Look at the source and try to figure out what the programs do, and run -them with various inputs. If you want to, look at the hints files for -spoilers - this year we included most of the information included -by the submitter. - Read over the makefile for compile/build issues. Your system may require certain changes (add or remove a library, add or remove a #define). @@ -88,10 +82,10 @@ For news of the next contest watch: > ------------------------------------------------------------------------------------------------------ -(c) Copyright 1984-2020, [Leo Broukhis, Simon Cooper, Landon Curt Noll][judges] - All rights reserved -This work is licensed under a [Creative Commons Attribution-ShareAlike 3.0 Unported License][cc]. +=-= -[judges]: http://www.ioccc.org/judges.html -[cc]: http://creativecommons.org/licenses/by-sa/3.0/ ------------------------------------------------------------------------------------------------------ +Copyright (C) 2020, 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.