update year level README files
Move copyright notice to the end. Add a standard comment about the newly added `README.md` files. Clean up trailing whitespace. Fixed a few minor typos.
This commit is contained in:
1 parent
5552243c7b
commit
b449cb503c
27 files changed
+338
-651
No files matched your search
@@ -1,135 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html>
|
||||
<head>
|
||||
<meta name="GENERATOR" content="mkd2html 2.1.5a DL=DISCOUNT">
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
|
||||
<link rel="stylesheet"
|
||||
type="text/css"
|
||||
href="hint.css">
|
||||
<title>README</title>
|
||||
</head>
|
||||
<body>
|
||||
<h1>2012 marked the “The Twenty First International Obfuscated C Code Contest”</h1>
|
||||
|
||||
<p>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.</p>
|
||||
|
||||
<h2>Standard IOCCC stuff</h2>
|
||||
|
||||
<p>The IOCCC has a web site and now has a number of international mirrors.
|
||||
The primary site can be found at <b>www.ioccc.org</b>.
|
||||
|
||||
<p>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.</p>
|
||||
|
||||
<p>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.</p>
|
||||
|
||||
<p>Read over the makefile for compile/build issues. Your system may require
|
||||
certain changes (add or remove a library, add or remove a #define).</p>
|
||||
|
||||
<p>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.</p>
|
||||
|
||||
<h2>Remarks on some of the entries</h2>
|
||||
|
||||
<p>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.</p>
|
||||
|
||||
<p>This year we selected the top 4 entries for particularly high honors:</p>
|
||||
|
||||
<ul>
|
||||
<li><p>Gold award - Balanced use of obfuscation</p>
|
||||
|
||||
<p>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!</p></li>
|
||||
<li><p>Silver award - Most elementary use of C</p>
|
||||
|
||||
<p>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.</p></li>
|
||||
<li><p>Bronze award - Best use of cocoa</p>
|
||||
|
||||
<p>A picture within a picture is worth more than a
|
||||
thousand (4 byte) words. :-)</p></li>
|
||||
<li><p>Honorable mention - Most complex ASCII fluid</p>
|
||||
|
||||
<p>When you see this program in action, you too will
|
||||
very likely say <a href="http://bit.ly/R6ALpK">wow</a> as we did!</p></li>
|
||||
</ul>
|
||||
|
||||
|
||||
<p>But don’t ignore the other winners! There are games, utilities,
|
||||
eye candy, calculators and graphical tools to explore.</p>
|
||||
|
||||
<p>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.</p>
|
||||
|
||||
<p>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? :-)</p>
|
||||
|
||||
<p>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!</p>
|
||||
|
||||
<p>There were some outstanding entries that did not win. Unfortunately
|
||||
some very good entries lost because they:</p>
|
||||
|
||||
<ul>
|
||||
<li><p>would take years to execute</p></li>
|
||||
<li><p>were way way oversize and didn’t even attempt to justify their
|
||||
excess by a clever abuse of the rules</p></li>
|
||||
<li><p>obfuscate themselves by simply invoking a complex
|
||||
state machine</p></li>
|
||||
<li><p>depend on a single obfuscation trick</p></li>
|
||||
<li><p>could only be run on a particular vendor’s platform</p></li>
|
||||
<li><p>were very similar to previous winners</p></li>
|
||||
<li><p>were based on an overused theme such as yet another
|
||||
fractal display program</p></li>
|
||||
<li><p>didn’t work as documented</p></li>
|
||||
</ul>
|
||||
|
||||
|
||||
<p>We hope the authors of some of those entries will fix and re-submit
|
||||
them for the next IOCCC.</p>
|
||||
|
||||
<p>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.</p>
|
||||
|
||||
<h2>Final Comments</h2>
|
||||
|
||||
<p>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.</p>
|
||||
|
||||
<p>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.</p>
|
||||
|
||||
<p>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).</p>
|
||||
|
||||
<TABLE><TR>
|
||||
<TD><a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/"><img alt="Creative Commons License" style="border-width:0" src="http://i.creativecommons.org/l/by-sa/3.0/88x31.png" /></a></TD>
|
||||
<TD><P>© Copyright 1984-2012,
|
||||
<A HREF="/judges.html">Leo Broukhis, Simon Cooper, Landon Curt Noll</A>
|
||||
- All rights reserved<BR>
|
||||
This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/">Creative Commons Attribution-ShareAlike 3.0 Unported License</a>.</P></TD>
|
||||
<TD> <!--<a href="http://validator.w3.org/check?uri=referer"><img src="http://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01 Transitional" height="31" width="88"></a>--></TD>
|
||||
</TR></TABLE>
|
||||
</body>
|
||||
</html>
|
||||
+11
-19
@@ -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:
|
||||
|
||||
> <http://www.ioccc.org/>
|
||||
|
||||
=-=
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
<!--
|
||||
(c) Copyright 1984-2012, [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) 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.
|
||||
Reference in new issue
Block a user