mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

force use of pandoc version >= 3.1.12.2

Browse Source 
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
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

2014/index.html
+65 -90
View File
@@ -123,87 +123,75 @@
<!-- 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-third-international-obfuscated-c-code-contest">Twenty
Third International Obfuscated C Code Contest</h1>
<h1 id="twenty-third-international-obfuscated-c-code-contest">Twenty Third 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 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">www.ioccc.org</a>.</p>
<p>Use make 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>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 README.md 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
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">www.ioccc.org</a>.</p>
<p>Use make 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>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 README.md 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 gcc 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 again be impressed with this year’s winning
entries.</p>
<h2 id="remarks-on-some-of-the-entries">Remarks on some of the entries</h2>
<p>We believe you will again be impressed with this year’s winning entries.</p>
<p>This year, 2014:</p>
<p>We, the judges, were very surprised by this as many of the multiple
authors submitted very different styles of entries.</p>
<p>This year was the second time the IOCCC size tool was used. Rule 2
required that when program source is fed as input to the current IOCCC
size tool, and the IOCCC size tool <code>-i</code> command line option
is used, the value printed should be less than or equal to 2053.</p>
<p>We were pleased to see that abuse of the rules was extended to abuse
to the IOCCC size tool. <a href="../authors.html#Matt_Zucker">Matt
Zucker</a>, followed by a few users, were able to discover clever use of
certain <code>//</code> comments to perplex the size tool. The abuse was
so bad that the judges released a critical and mandatory patch to the
IOCCC size tool on 2014-09-23.</p>
<p>There were some great entries that did not win. Unfortunately some
entries lost because they:</p>
required that when program source is fed as input to the current IOCCC size
tool, and the IOCCC size tool <code>-i</code> command line option is used, the value
printed should be less than or equal to 2053.</p>
<p>We were pleased to see that abuse of the rules was extended to abuse to the
IOCCC size tool. <a href="../authors.html#Matt_Zucker">Matt Zucker</a>, followed by a few
users, were able to discover clever use of certain <code>//</code> comments to perplex the
size tool. The abuse was so bad that the judges released a critical and
mandatory patch to the IOCCC size tool on 2014-09-23.</p>
<p>There were some great entries that did not win. Unfortunately
some entries lost because they:</p>
<ul>
<li><p>were too large according the IOCCC size tool and didn’t even
attempt to justify their excess by a clever abuse of the rules</p></li>
<li><p>were too large according the IOCCC size tool and didn’t
even attempt to justify their excess by a clever abuse of the rules</p></li>
<li><p>depended on a single obfuscation trick</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 winning entries. Previous authors set a very high bar.
A new winning entry must not only compete against submissions from the
current year, they must also excel over any similar entries in some
particularly impressive way.</p>
<h2 id="on-the-delay-in-releasing-the-winning-entries">On the delay in
releasing the winning entries</h2>
<p>There is a risk in submitting an entry that is similar to a well
used theme by previous winning entries. Previous authors set a very high
bar. A new winning entry must not only compete against submissions
from the current year, they must also excel over any similar entries
in some particularly impressive way.</p>
<h2 id="on-the-delay-in-releasing-the-winning-entries">On the delay in releasing the winning entries</h2>
<p>We apologize on the delay of sending the authors the tarball for them
to review. There were some unforeseen events, such as unplanned
mandatory business travel, the death of an IOCCC judge’s mother, etc.
that impacted our planned schedule for building the tarball of this
year’s winning entries.</p>
<p>During some of these forced delays, we took the time to better
automate some of the tools needed to package the source for the winning
entries to review and to post the edited entries to the web site. It is
our intent that these changes made during those delays will make
releasing future winning IOCCC entries a faster procedure.</p>
<p>p.s. The final advice given to Landon by his mom: “Have fun.” We
recommend following this advice where possible.</p>
to review. There were some unforeseen events, such as unplanned mandatory
business travel, the death of an IOCCC judge’s mother, etc. that impacted
our planned schedule for building the tarball of this year’s winning entries.</p>
<p>During some of these forced delays, we took the time to better automate
some of the tools needed to package the source for the winning entries to review
and to post the edited entries to the web site. It is our intent that
these changes made during those delays will make releasing future winning IOCCC
entries a faster procedure.</p>
<p>p.s. The final advice given to Landon by his mom: “Have fun.”
We recommend following this advice where possible.</p>
<h2 id="final-comments">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>
<p>For the latest information on how to contact the IOCCC Judges please
visit</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>
<ul>
<li><a href="../contact.html">contact.html</a></li>
</ul>
@@ -212,41 +200,28 @@ visit</p>
<li><a href="../news/html">news.html</a></li>
</ul>
<h1 id="copyright-and-license">Copyright and License</h1>
<p>Copyright (C) 2014,2024, 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) 2014,2024, 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-2014---the-23rd-ioccc"><a name=inventory></a><a name=2014></a>Winning
Entries of 2014 - The 23rd IOCCC</h1>
<p><strong>Download IOCCC</strong> <a
href="2014/ioccc.2014.tar.bz2">2014 entry source</a></p>
<h1 id="winning-entries-of-2014---the-23rd-ioccc"><a name=inventory></a><a name=2014></a>Winning Entries of 2014 - The 23rd IOCCC</h1>
<p><strong>Download IOCCC</strong> <a href="2014/ioccc.2014.tar.bz2">2014 entry source</a></p>
<ul>
<li><a href="birken/index.html">2014/birken</a> - Best use of port
1701</li>
<li><a href="deak/index.html">2014/deak</a> - Most underscored
argument</li>
<li><a href="endoh1/index.html">2014/endoh1</a> - Most square (YODA
award)</li>
<li><a href="endoh2/index.html">2014/endoh2</a> - Best use of
bioinformatics</li>
<li><a href="maffiodo1/index.html">2014/maffiodo1</a> - Homage to a
classic game</li>
<li><a href="maffiodo2/index.html">2014/maffiodo2</a> - Most tweetable
entry</li>
<li><a href="morgan/index.html">2014/morgan</a> - Most likely to
succeed</li>
<li><a href="sinon/index.html">2014/sinon</a> - Best choice of
optimization</li>
<li><a href="birken/index.html">2014/birken</a> - Best use of port 1701</li>
<li><a href="deak/index.html">2014/deak</a> - Most underscored argument</li>
<li><a href="endoh1/index.html">2014/endoh1</a> - Most square (YODA award)</li>
<li><a href="endoh2/index.html">2014/endoh2</a> - Best use of bioinformatics</li>
<li><a href="maffiodo1/index.html">2014/maffiodo1</a> - Homage to a classic game</li>
<li><a href="maffiodo2/index.html">2014/maffiodo2</a> - Most tweetable entry</li>
<li><a href="morgan/index.html">2014/morgan</a> - Most likely to succeed</li>
<li><a href="sinon/index.html">2014/sinon</a> - Best choice of optimization</li>
<li><a href="skeggs/index.html">2014/skeggs</a> - Most dynamic</li>
<li><a href="vik/index.html">2014/vik</a> - Best handling of beeps</li>
<li><a href="wiedijk/index.html">2014/wiedijk</a> - Most functional</li>