Add preview of 1984-2019
The 2020 winners are hinted it, but the source code is not there,
nor are the hints. Someone could look into the HTML and
see what was commented out, but that is not a problem because
WHO won is known and the name of their AWARD is known already.
Moreover a number of the winners have talked about what their
entirs do, so the commented out spoiler text is not a bit problem.
One will find HTML commented out with:
<!-- XXX remove when 2020 is ready
2020 links here
XXX remove when 2020 is ready -->
The "XXX remove when 2020 is ready" string is found at the
start and end comment blocks. Again, soneone could read
what was commented out, but that is OK since most of that
information is known or can be known. The following files
have such HTML comment blocks in them.
./winners.html
./years-spoiler.html
./years.html
In addition, ./all/summary.txt was modified to not
include the 2020 entries for the momemt.
The 2020 winner code AND write-ups are NOT part of this set.
p.s. The all/all.tar.bz2 does not contain the 2020 source code (yet?).
This commit is contained in:
Landon Curt Noll committed
1 parent
28efc67f5d
commit
c0663537cb
1683 files changed
+220064
No files matched your search
+126
@@ -0,0 +1,126 @@
|
||||
<!doctype html public "-//W3C//DTD HTML 4.0 Transitional //EN">
|
||||
<html>
|
||||
<head>
|
||||
<meta name="GENERATOR" content="mkd2html 2.2.2">
|
||||
<meta http-equiv="Content-Type"
|
||||
content="text/html; charset=utf-8"> <link rel="stylesheet"
|
||||
type="text/css"
|
||||
href="hint.css" />
|
||||
<title></title>
|
||||
<title>README</title>
|
||||
</head>
|
||||
<body>
|
||||
<CENTER>
|
||||
<IMG SRC="/png/ioccc.png" ALT="IOCCC" height=78 width=267>
|
||||
<P><FONT size="6"><I>The International Obfuscated C Code Contest</I></FONT></P>
|
||||
<div id="bar">
|
||||
<ul>
|
||||
<li><a href="index.html">About the 27th IOCCC</a></li>
|
||||
<li><a href="whowon.html">27th IOCCC Winners</a></li>
|
||||
<li><a href="/index.html">IOCCC home</a></li>
|
||||
<li><a href="/winners.html">List of All Winners</a></li>
|
||||
<li><a href="/judges.html">The Judges</a></li>
|
||||
</ul>
|
||||
</div>
|
||||
<P><FONT size="6"><B>The 27<sup>th</sup> IOCCC</B></FONT></P>
|
||||
</CENTER>
|
||||
|
||||
|
||||
<h2>2020 marked the “The Twenty Seventh International Obfuscated C Code Contest”</h2>
|
||||
|
||||
<p>Copyright © 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.</p>
|
||||
|
||||
<h2>Standard IOCCC stuff</h2>
|
||||
|
||||
<p>The primary IOCCC web site can be found at,</p>
|
||||
|
||||
<blockquote><p> <a href="http://www.ioccc.org/">http://www.ioccc.org/</a></p></blockquote>
|
||||
|
||||
<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 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.</p>
|
||||
|
||||
<h2>Remarks on some of the winners</h2>
|
||||
|
||||
<p>This year’s Best of Show (carlini) is such a novel way of obfuscation that it would be
|
||||
worth of a special mention in the (future) Best of IOCCC list!</p>
|
||||
|
||||
<p>For some reason, this year’s set of winners contains three nostalgic games,
|
||||
Asteroids (tsoj), Minesweeper (endoh1), and Snake (ferguson1).</p>
|
||||
|
||||
<p>An entry (kurdyukov1) pays homage to a previous winner (2015/hou).</p>
|
||||
|
||||
<p>…We’ll stop spouting spoilers now. Have fun exploring all the entries!</p>
|
||||
|
||||
<h2>Remarks on some of submissions that did not win</h2>
|
||||
|
||||
<p>As a rule, we try to compile the entries on a variety of platforms.
|
||||
Quite a few entries this year could not be built or executed on some of them due to reliance on
|
||||
library internals or the system runtime.</p>
|
||||
|
||||
<p>A few entries were violating the “2053 significant bytes” rule. If an entry could not be brought to
|
||||
compliance within a few seconds of looking at the source, it was disqualified.</p>
|
||||
|
||||
<p>One entry tried to get around the size limit by putting the code into
|
||||
makefile variables and using -D. This is already called out as discouraged
|
||||
technique in the guidelines, but it is worth a reminder.</p>
|
||||
|
||||
<p>Several promising entries attempted to make use of the <code>syscall</code> function using literal syscall numbers.
|
||||
This is utterly non-portable.</p>
|
||||
|
||||
<p>A note to the authors: when submitting multiple entries, don’t let us easily correlate them by
|
||||
coding style or documentation content, and definitely don’t submit nearly identical versions
|
||||
of your program separately. As we try to judge the entries anonymously, the similarities will cause such
|
||||
entries to compete against one another, making each less likely to win.</p>
|
||||
|
||||
<p>We hope the authors of non-winning entries will refine their entries and
|
||||
perhaps re-submit them for the next IOCCC.</p>
|
||||
|
||||
<h2>Final Comments</h2>
|
||||
|
||||
<p>One more thing that feels dated is digraphs and trigraphs.</p>
|
||||
|
||||
<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>
|
||||
|
||||
<p>For the latest information on how to contact the IOCCC Judges please visit</p>
|
||||
|
||||
<blockquote><p> <a href="http://www.ioccc.org/contact.html">http://www.ioccc.org/contact.html</a></p></blockquote>
|
||||
|
||||
<p>For news of the next contest watch:</p>
|
||||
|
||||
<blockquote><p> <a href="http://www.ioccc.org/">http://www.ioccc.org/</a></p></blockquote>
|
||||
<BR>
|
||||
<HR>
|
||||
<TABLE><TR>
|
||||
<TD><a rel="license" href="https://creativecommons.org/licenses/by-sa/3.0/"><img alt="Creative Commons License" style="border-width:0" src="/png/by-sa-3.0-88x31.png" /></a></TD>
|
||||
<TD><P>© Copyright 1984-2020,
|
||||
<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="https://creativecommons.org/licenses/by-sa/3.0/">Creative Commons Attribution-ShareAlike 3.0 Unported License</a>.</P></TD>
|
||||
<TD> <!--<a href="https://validator.w3.org/check?uri=referer"><img src="https://www.w3.org/Icons/valid-html401" alt="Valid HTML 4.01 Transitional" height="31" width="88"></a>--></TD>
|
||||
</TR></TABLE>
|
||||
</body>
|
||||
</html>
|
||||
Reference in new issue
Block a user