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 2024-03-18 01:26:39 -07:00
1 parent 9eb7a54e9f
commit b0b212acb1
402 files changed
+37061 -55132

No files matched your search

+50 -79
View File
@@ -123,32 +123,27 @@
<!-- 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="twenty-sixth-international-obfuscated-c-code-contest">Twenty
Sixth International Obfuscated C Code Contest</h1>
<h1 id="twenty-sixth-international-obfuscated-c-code-contest">Twenty Sixth 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 it 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 primary site can be found at <a
href="https://www.ioccc.org">www.ioccc.org</a>.</p>
<p>Use <code>make</code> to compile entries. It is possible that on
non-Unix / non-Linux systems the Makefile needs to be changed. See the
Makefile for details.</p>
<p>Read over the Makefile and index.html files 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 it 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 primary site can be found at <a href="https://www.ioccc.org">www.ioccc.org</a>.</p>
<p>Use <code>make</code> to compile entries. It is possible that on non-Unix / non-Linux
systems the Makefile needs to be changed. See the Makefile for details.</p>
<p>Read over the Makefile and index.html files 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 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 id="remarks-on-some-of-the-winning-entries">Remarks on some of the
winning entries</h2>
lacking, you may need to compile using clang or gcc instead of your local
compiler.</p>
<h2 id="remarks-on-some-of-the-winning-entries">Remarks on some of the winning entries</h2>
<p>This year’s winning entries are impressive!</p>
<p>The <a href="endoh/index.html">“Most in need of debugging”
(endoh)</a> is very inventive in a way it produces its own text!</p>
<p>The <a href="ciura/index.html">“Most likely to be awarded”
(ciura)</a> has an amazing vocabulary!</p>
<p>The <a href="endoh/index.html">“Most in need of debugging” (endoh)</a> is very inventive in
a way it produces its own text!</p>
<p>The <a href="ciura/index.html">“Most likely to be awarded” (ciura)</a> has an amazing
vocabulary!</p>
<p>There are again nods to entries of the years:</p>
<pre><code>[1991/davidguy](../years.html#1991_davidguy)
[2011/blakely](../years.html#2011_blakely)</code></pre>
@@ -156,79 +151,55 @@ winning entries</h2>
<pre><code>We tend to dislike programs that:
...
are rather similar to previous entries</code></pre>
<p>because the entry <a href="2019/dogon/index.html">2019/dogon</a>
appropriately pays homage to past entries without blatantly reusing
their code.</p>
<p>…We’ll stop spouting spoilers now. Have fun exploring all the
entries!</p>
<h2 id="remarks-on-some-of-submissions-that-did-not-win">Remarks on some
of submissions that did not win</h2>
<p>because the entry <a href="2019/dogon/index.html">2019/dogon</a> appropriately pays homage
to past entries without blatantly reusing their code.</p>
<p>…We’ll stop spouting spoilers now. Have fun exploring all the entries!</p>
<h2 id="remarks-on-some-of-submissions-that-did-not-win">Remarks on some of submissions that did not win</h2>
<p>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.</p>
file that was really C code and then blindly including code in prog.c.</p>
<p>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.</p>
<p>Using extra arguments to <code>main</code>, or arguments of wrong
types as a quick and dirty way of declaring variables is now passé.
Clang, for example, rejects them outright.</p>
uninitialized locals and/or reading-writing below the stack.
We advise running your entry through valgrind to make sure those mistakes
are avoided.</p>
<p>Using extra arguments to <code>main</code>, or arguments of wrong types as a quick and dirty
way of declaring variables is now passé. Clang, for example, rejects them outright.</p>
<p>We hope the authors of some of those entries will fix and re-submit
them for the next IOCCC.</p>
<p>Some entries seemed to have a good idea, but the implementation of
the idea was limited in scope.</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) 2019,2023, Landon Curt Noll 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) 2019,2023, Landon Curt Noll 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-2019---the-26th-ioccc"><a name=inventory></a><a name=2019></a>Winning
Entries of 2019 - The 26th IOCCC</h1>
<p><strong>Download IOCCC</strong> <a
href="2019/ioccc.2019.tar.bz2">2019 entry source</a></p>
<h1 id="winning-entries-of-2019---the-26th-ioccc"><a name=inventory></a><a name=2019></a>Winning Entries of 2019 - The 26th IOCCC</h1>
<p><strong>Download IOCCC</strong> <a href="2019/ioccc.2019.tar.bz2">2019 entry source</a></p>
<ul>
<li><a href="adamovsky/index.html">2019/adamovsky</a> - Most functional
interpreter</li>
<li><a href="adamovsky/index.html">2019/adamovsky</a> - Most functional interpreter</li>
<li><a href="burton/index.html">2019/burton</a> - Best one-liner</li>
<li><a href="ciura/index.html">2019/ciura</a> - Most alphabetic</li>
<li><a href="diels-grabsch1/index.html">2019/diels-grabsch1</a> - Best
small program</li>
<li><a href="diels-grabsch2/index.html">2019/diels-grabsch2</a> - Most
self-aware</li>
<li><a href="dogon/index.html">2019/dogon</a> - Best use of space and
time</li>
<li><a href="duble/index.html">2019/duble</a> - Best collaborative
graphics</li>
<li><a href="endoh/index.html">2019/endoh</a> - Most in need of
debugging</li>
<li><a href="giles/index.html">2019/giles</a> - Most in need of wide
space</li>
<li><a href="karns/index.html">2019/karns</a> - Most in need of
whitespace</li>
<li><a href="lynn/index.html">2019/lynn</a> - Most functional
compiler</li>
<li><a href="mills/index.html">2019/mills</a> - Most in need to be
tweeted</li>
<li><a href="poikola/index.html">2019/poikola</a> - Most
calendrical</li>
<li><a href="yang/index.html">2019/yang</a> - Most in need of
transparency</li>
<li><a href="diels-grabsch1/index.html">2019/diels-grabsch1</a> - Best small program</li>
<li><a href="diels-grabsch2/index.html">2019/diels-grabsch2</a> - Most self-aware</li>
<li><a href="dogon/index.html">2019/dogon</a> - Best use of space and time</li>
<li><a href="duble/index.html">2019/duble</a> - Best collaborative graphics</li>
<li><a href="endoh/index.html">2019/endoh</a> - Most in need of debugging</li>
<li><a href="giles/index.html">2019/giles</a> - Most in need of wide space</li>
<li><a href="karns/index.html">2019/karns</a> - Most in need of whitespace</li>
<li><a href="lynn/index.html">2019/lynn</a> - Most functional compiler</li>
<li><a href="mills/index.html">2019/mills</a> - Most in need to be tweeted</li>
<li><a href="poikola/index.html">2019/poikola</a> - Most calendrical</li>
<li><a href="yang/index.html">2019/yang</a> - Most in need of transparency</li>
</ul>
<p> <strong>Jump to:</strong> <a href="#">top</a></p>