force use of pandoc version >= 3.1.12.2
The `bin/pandoc-wrapper.sh` tool will verify that the ssytem has a recent enough version of `pandoc(1)`. We explain why we insist on `pandoc(1)`. version >= 3.1.12.2 in comments where the $PANDOC_MIN_VERSION is set. Added `--wrap=preserve` as a default argument to `pandoc(1)`. While this change will impact every HTML file generated, we believe this will improve the ability of someone to look at the generated HTML and correlate with the original markdown. Changed `bin/pandoc-wrapper.sh` VERSION from "1.4.2 2024-03-17" to "1.4.3 2024-03-18". Performed `make www` to achieve all of the above and to generate HTML using the new `--wrap=preserve` `pandoc(1)` mode.
This commit is contained in:
Landon Curt Noll committed
1 parent
9eb7a54e9f
commit
b0b212acb1
402 files changed
+37061
-55132
No files matched your search
+50
-79
@@ -123,50 +123,40 @@
|
||||
<!-- END: this line ends content from: inc/before-content.default.html -->
|
||||
<!-- START: this line starts content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
|
||||
|
||||
<h1 id="seventeenth-international-obfuscated-c-code-contest">Seventeenth
|
||||
International Obfuscated C Code Contest</h1>
|
||||
<h1 id="seventeenth-international-obfuscated-c-code-contest">Seventeenth International Obfuscated C Code Contest</h1>
|
||||
<h2 id="standard-ioccc-stuff">Standard IOCCC stuff</h2>
|
||||
<p>View the <code>index.html</code> web page for the given winning entry
|
||||
for information on how 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.</p>
|
||||
<p>The IOCCC has a web site and now has a number of international
|
||||
mirrors. The primary site can be found at <a
|
||||
href="https://www.ioccc.org/"
|
||||
class="uri">https://www.ioccc.org/</a>.</p>
|
||||
<p>Use <code>make(1)</code> to compile entries. It is possible that on
|
||||
non-Unix / non-Linux systems the <code>Makefile</code> needs to be
|
||||
changed. See the <code>Makefile</code> for details.</p>
|
||||
<p>Read over the <code>Makefile</code> for compile/build issues. Your
|
||||
system may require certain changes (add or remove a library, add or
|
||||
remove a <code>#define</code>).</p>
|
||||
<p>View the <code>index.html</code> web page for the given winning entry for information on how
|
||||
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.</p>
|
||||
<p>The IOCCC has a web site and now has a number of international mirrors.
|
||||
The primary site can be found at <a href="https://www.ioccc.org/" class="uri">https://www.ioccc.org/</a>.</p>
|
||||
<p>Use <code>make(1)</code> to compile entries. It is possible that on non-Unix / non-Linux
|
||||
systems the <code>Makefile</code> needs to be changed. See the <code>Makefile</code> for details.</p>
|
||||
<p>Read over the <code>Makefile</code> for compile/build issues. Your system may
|
||||
require certain changes (add or remove a library, add or remove a
|
||||
<code>#define</code>).</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 <code>gcc</code> instead
|
||||
of your local compiler.</p>
|
||||
<h2 id="remarks-on-some-of-the-entries">Remarks on some of the
|
||||
entries</h2>
|
||||
<p>We believe you will be impressed with this year’s winning entries.
|
||||
The <a href="gavin/gavin.c">Best of Show</a> is a fine example of
|
||||
obfuscation. But don’t ignore the other entries! There are games,
|
||||
utilities, programs that output images and a one-liner that is
|
||||
incredibly compact for what it can do.</p>
|
||||
<p>The <a href="hibachi/hibachi.c">Best Abuse of the Guidelines</a> is
|
||||
technically allowed by the rules. This year we allowed it due to the
|
||||
functionality of the program. This entry is one of the easiest to read!
|
||||
Don’t assume you can win using similar techniques next time … :-)</p>
|
||||
<p>This year a <a href="../authors.html#Daniel_Vik">single person</a>
|
||||
won two awards! We also had repeat authors with their 6th, 4th and 2nd
|
||||
winning entries this year! (Please note that judging is done completely
|
||||
anonymously. Be warned that we may disqualify entries that reveal the
|
||||
identity of the submitter.)</p>
|
||||
<h3 id="remarks-on-some-losing-entries">Remarks on some losing
|
||||
entries</h3>
|
||||
yours is lacking, you may need to compile using <code>gcc</code> instead of your
|
||||
local compiler.</p>
|
||||
<h2 id="remarks-on-some-of-the-entries">Remarks on some of the entries</h2>
|
||||
<p>We believe you will be impressed with this year’s winning entries. The <a href="gavin/gavin.c">Best of
|
||||
Show</a> is a fine example of obfuscation. But don’t ignore the
|
||||
other entries! There are games, utilities, programs that output images and a
|
||||
one-liner that is incredibly compact for what it can do.</p>
|
||||
<p>The <a href="hibachi/hibachi.c">Best Abuse of the Guidelines</a> is technically allowed by
|
||||
the rules. This year we allowed it due to the functionality of the program.
|
||||
This entry is one of the easiest to read! Don’t assume you can win using
|
||||
similar techniques next time … :-)</p>
|
||||
<p>This year a <a href="../authors.html#Daniel_Vik">single person</a> won two awards! We also
|
||||
had repeat authors with their 6th, 4th and 2nd winning entries this year!
|
||||
(Please note that judging is done completely anonymously. Be warned that we may
|
||||
disqualify entries that reveal the identity of the submitter.)</p>
|
||||
<h3 id="remarks-on-some-losing-entries">Remarks on some losing entries</h3>
|
||||
<p>There were some outstanding entries that did not win. Unfortunately
|
||||
some very good entries lost because they:</p>
|
||||
<ul>
|
||||
<li>depended too much on non-portable side effects in expressions;
|
||||
and/or</li>
|
||||
<li>depended too much on non-portable side effects in expressions; and/or</li>
|
||||
<li>depended too much on a particular byte order; and/or</li>
|
||||
<li>required the use of a special script, data file or pseudo-machine
|
||||
language that was not supplied with the entry.</li>
|
||||
@@ -174,56 +164,37 @@ language that was not supplied with the entry.</li>
|
||||
<p>We hope the authors of some of those entries will fix and re-submit
|
||||
them for the next IOCCC.</p>
|
||||
<h2 id="final-comments">Final Comments</h2>
|
||||
<p><strong>IMPORTANT NOTE</strong>: See <a
|
||||
href="../contact.html">contact.html</a> for up to date contact details
|
||||
as well as details on how to provide fixes to any of the entries. See
|
||||
also <a href="../faq.html">the IOCCC FAQ</a> for addition information on
|
||||
the IOCCC.</p>
|
||||
<p><strong>IMPORTANT NOTE</strong>: See <a href="../contact.html">contact.html</a> for up to date contact details
|
||||
as well as details on how to provide fixes to any of the entries.
|
||||
See also <a href="../faq.html">the IOCCC FAQ</a> for addition information on the IOCCC.</p>
|
||||
<h1 id="copyright-and-license">Copyright and License</h1>
|
||||
<p>Copyright (c) 2001,2004,2023, Landon Curt Noll, Peter Seebach and
|
||||
Leonid A. Broukhis. All Rights Reserved. This work is licensed under a
|
||||
<a href="https://creativecommons.org/licenses/by-sa/4.0/">Creative
|
||||
Commons CC BY-SA 4.0 DEED Attribution-ShareAlike 4.0 International</a>
|
||||
license. If you do use this work in some form, the <a
|
||||
href="../judges.html">IOCCC judges</a> would appreciate (but does not
|
||||
require) if you were to <a href="../contact.html">send us a note about
|
||||
your use</a>.</p>
|
||||
<p>Copyright (c) 2001,2004,2023, Landon Curt Noll, Peter Seebach and Leonid A. Broukhis. All Rights Reserved.
|
||||
This work is licensed under a <a href="https://creativecommons.org/licenses/by-sa/4.0/">Creative Commons CC BY-SA 4.0 DEED Attribution-ShareAlike
|
||||
4.0 International</a> license.
|
||||
If you do use this work in some form, the <a href="../judges.html">IOCCC judges</a> would appreciate
|
||||
(but does not require) if you were to <a href="../contact.html">send us a note about your use</a>.</p>
|
||||
|
||||
<!-- END: this line ends content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
|
||||
<!-- START: this line starts content for HTML phase 22 by: bin/output-year-index.sh via bin/md2html.sh -->
|
||||
|
||||
<!-- START: this line starts content generated by: bin/output-year-index.sh -->
|
||||
|
||||
<h1
|
||||
id="winning-entries-of-2004---the-17th-ioccc"><a name=inventory></a><a name=2004></a>Winning
|
||||
Entries of 2004 - The 17th IOCCC</h1>
|
||||
<p><strong>Download IOCCC</strong> <a
|
||||
href="2004/ioccc.2004.tar.bz2">2004 entry source</a></p>
|
||||
<h1 id="winning-entries-of-2004---the-17th-ioccc"><a name=inventory></a><a name=2004></a>Winning Entries of 2004 - The 17th IOCCC</h1>
|
||||
<p><strong>Download IOCCC</strong> <a href="2004/ioccc.2004.tar.bz2">2004 entry source</a></p>
|
||||
<ul>
|
||||
<li><a href="anonymous/index.html">2004/anonymous</a> - “Best use
|
||||
of”“Precious”” Lines”</li>
|
||||
<li><a href="arachnid/index.html">2004/arachnid</a> - Best use of
|
||||
Vision</li>
|
||||
<li><a href="burley/index.html">2004/burley</a> - Best Calculated
|
||||
Risk</li>
|
||||
<li><a href="gavare/index.html">2004/gavare</a> - Best Use of Light and
|
||||
Spheres</li>
|
||||
<li><a href="anonymous/index.html">2004/anonymous</a> - “Best use of”“Precious”” Lines”</li>
|
||||
<li><a href="arachnid/index.html">2004/arachnid</a> - Best use of Vision</li>
|
||||
<li><a href="burley/index.html">2004/burley</a> - Best Calculated Risk</li>
|
||||
<li><a href="gavare/index.html">2004/gavare</a> - Best Use of Light and Spheres</li>
|
||||
<li><a href="gavin/index.html">2004/gavin</a> - Best of Show</li>
|
||||
<li><a href="hibachi/index.html">2004/hibachi</a> - Best Abuse of the
|
||||
Guidelines</li>
|
||||
<li><a href="hoyle/index.html">2004/hoyle</a> - Most Functional
|
||||
Output</li>
|
||||
<li><a href="jdalbec/index.html">2004/jdalbec</a> - Best Abuse of the
|
||||
Periodic Table</li>
|
||||
<li><a href="kopczynski/index.html">2004/kopczynski</a> - Best
|
||||
One-Liner</li>
|
||||
<li><a href="newbern/index.html">2004/newbern</a> - Best Font
|
||||
Engine</li>
|
||||
<li><a href="hibachi/index.html">2004/hibachi</a> - Best Abuse of the Guidelines</li>
|
||||
<li><a href="hoyle/index.html">2004/hoyle</a> - Most Functional Output</li>
|
||||
<li><a href="jdalbec/index.html">2004/jdalbec</a> - Best Abuse of the Periodic Table</li>
|
||||
<li><a href="kopczynski/index.html">2004/kopczynski</a> - Best One-Liner</li>
|
||||
<li><a href="newbern/index.html">2004/newbern</a> - Best Font Engine</li>
|
||||
<li><a href="omoikane/index.html">2004/omoikane</a> - Best Utility</li>
|
||||
<li><a href="schnitzi/index.html">2004/schnitzi</a> - Best Non-Use of
|
||||
Curses</li>
|
||||
<li><a href="sds/index.html">2004/sds</a> - Best Abuse of
|
||||
Indentation</li>
|
||||
<li><a href="schnitzi/index.html">2004/schnitzi</a> - Best Non-Use of Curses</li>
|
||||
<li><a href="sds/index.html">2004/sds</a> - Best Abuse of Indentation</li>
|
||||
<li><a href="vik1/index.html">2004/vik1</a> - Best X11 Game</li>
|
||||
<li><a href="vik2/index.html">2004/vik2</a> - Best Abuse of CPP</li>
|
||||
</ul>
|
||||
|
||||
Reference in new issue
Block a user