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:
1 parent
9eb7a54e9f
commit
b0b212acb1
402 files changed
+37061
-55132
No files matched your search
+44
-74
@@ -130,8 +130,8 @@
|
||||
<h2 id="author"><a name="author"></a>Author:</h2>
|
||||
<ul>
|
||||
<li>Name: <a href="../../authors.html#Uri_Goren">Uri Goren</a><br>
|
||||
Location: <a href="../../location.html#IL">IL</a> - <em>State of
|
||||
Israel</em> (<em>Israel</em>) <br><br></li>
|
||||
Location: <a href="../../location.html#IL">IL</a> - <em>State of Israel</em> (<em>Israel</em>)
|
||||
<br><br></li>
|
||||
</ul>
|
||||
|
||||
<!-- END: next line ends content generated by: bin/output-index-author.sh -->
|
||||
@@ -146,12 +146,9 @@ Israel</em> (<em>Israel</em>) <br><br></li>
|
||||
<h2 id="try">Try:</h2>
|
||||
<div class="sourceCode" id="cb3"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb3-1"><a href="#cb3-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./try.sh</span></span></code></pre></div>
|
||||
<h2 id="judges-remarks">Judges’ remarks:</h2>
|
||||
<p>In the words of <a
|
||||
href="http://en.wikipedia.org/wiki/Rene_Magritte">René François Ghislain
|
||||
Magritte Magritte</a>:</p>
|
||||
<p>In the words of <a href="http://en.wikipedia.org/wiki/Rene_Magritte">René François Ghislain Magritte Magritte</a>:</p>
|
||||
<figure>
|
||||
<img src="MagrittePipe.jpg" title="Ceci n'est pas une pipe"
|
||||
alt="This is not a pipe" />
|
||||
<img src="MagrittePipe.jpg" title="Ceci n'est pas une pipe" alt="This is not a pipe" />
|
||||
<figcaption aria-hidden="true">This is not a pipe</figcaption>
|
||||
</figure>
|
||||
<p>One may ask the surrealist question:</p>
|
||||
@@ -160,96 +157,69 @@ alt="This is not a pipe" />
|
||||
<div class="sourceCode" id="cb5"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb5-1"><a href="#cb5-1" aria-hidden="true" tabindex="-1"></a><span class="bu">echo</span> <span class="st">'| is just a representation of a pipe because I say so! So stuff it!'</span> <span class="kw">|</span> <span class="ex">./goren</span></span></code></pre></div>
|
||||
<p>something happens! Why?</p>
|
||||
<h2 id="authors-remarks">Author’s remarks:</h2>
|
||||
<p>This program was written in homage to <a
|
||||
href="http://en.wikipedia.org/wiki/Rene_Magritte">Rene Magritte</a>’s
|
||||
picture <a
|
||||
href="https://en.wikipedia.org/wiki/The_Treachery_of_Images">“La
|
||||
trahison des images” (The Treachery of Images)</a>.</p>
|
||||
<p>This program was written in homage to <a href="http://en.wikipedia.org/wiki/Rene_Magritte">Rene
|
||||
Magritte</a>’s picture <a href="https://en.wikipedia.org/wiki/The_Treachery_of_Images">“La
|
||||
trahison des images” (The Treachery of
|
||||
Images)</a>.</p>
|
||||
<p>In order to show my unconditional admiration of this work, I avoided
|
||||
using conditions.</p>
|
||||
<p>In this work, Magritte points out that a picture of a pipe is not a
|
||||
pipe. But what IS a pipe? This program tries to provide an answer.</p>
|
||||
<p>Magritte’s <a
|
||||
href="http://en.wikipedia.org/wiki/The_Treachery_of_Images">test for
|
||||
pipes</a> is:</p>
|
||||
<p>In this work, Magritte points out that a picture of a pipe is not
|
||||
a pipe. But what IS a pipe? This program tries to provide an answer.</p>
|
||||
<p>Magritte’s <a href="http://en.wikipedia.org/wiki/The_Treachery_of_Images">test for pipes</a> is:</p>
|
||||
<pre><code>The famous pipe. How people reproached me for it! And yet, could
|
||||
you stuff my pipe? No, it's just a representation, is it not?</code></pre>
|
||||
<p>Accordingly, this program only approves pipes which can be used for
|
||||
stuffing data.</p>
|
||||
<p>One thing I tried to achieve is condition free programming. Many have
|
||||
noted that conditions make the code harder to read and understand. A
|
||||
good example would be: <a href="../../authors.html#Brent_Burley">Brent
|
||||
Burley</a>’s winning <a
|
||||
href="../../2004/burley/index.html">2004/burley</a> entry.</p>
|
||||
<p>That entry omits conditional statements such as <code>if</code> and
|
||||
<code>while</code>. His achievement in improving clarity by omitting
|
||||
conditions is impressive, but I think it can be taken further, in two
|
||||
ways.</p>
|
||||
<p>First, conditional operators, such as <code>?:</code>,
|
||||
<code>&&</code> and <code>||</code>, can be thrown away. Second,
|
||||
using <code>setjmp(3)</code> and <code>longjmp(3)</code>, which are
|
||||
unfortunately not in common use, might make it difficult for a novice
|
||||
programmer to understand the code without referring to the man page.</p>
|
||||
<p>One thing I tried to achieve is condition free programming. Many
|
||||
have noted that conditions make the code harder to read and understand.
|
||||
A good example would be: <a href="../../authors.html#Brent_Burley">Brent Burley</a>’s
|
||||
winning <a href="../../2004/burley/index.html">2004/burley</a> entry.</p>
|
||||
<p>That entry omits conditional statements such as <code>if</code> and <code>while</code>.
|
||||
His achievement in improving clarity by omitting conditions is
|
||||
impressive, but I think it can be taken further, in two ways.</p>
|
||||
<p>First, conditional operators, such as <code>?:</code>, <code>&&</code> and <code>||</code>, can be thrown away.
|
||||
Second, using <code>setjmp(3)</code> and <code>longjmp(3)</code>, which are unfortunately not in
|
||||
common use, might make it difficult for a novice programmer to understand the
|
||||
code without referring to the man page.</p>
|
||||
<p>By removing these, the code is 100% condition free, and every
|
||||
function runs its instructions in perfect order. Naturally, this makes
|
||||
the program flow trivial to understand. This can be verified by
|
||||
disassembling the compiled code and looking for conditional jumps (when
|
||||
compiled with gcc on x86, there are none).</p>
|
||||
function runs its instructions in perfect order. Naturally, this
|
||||
makes the program flow trivial to understand. This can be verified
|
||||
by disassembling the compiled code and looking for conditional jumps
|
||||
(when compiled with gcc on x86, there are none).</p>
|
||||
<h3 id="compatibility">Compatibility:</h3>
|
||||
<p>The program should compile with any C compiler, but was tested mostly
|
||||
with gcc on Linux.</p>
|
||||
<p>It doesn’t support 64 bits (due to integer-pointer casts, and
|
||||
<code>a >>31</code>). It does work on 64-bit Linux, because all
|
||||
functions are below 4GB.</p>
|
||||
<h2 id="copyright-and-cc-by-sa-4.0-license">Copyright and CC BY-SA 4.0
|
||||
License:</h2>
|
||||
<p>This file is Copyright (c) 2023 by Landon Curt Noll. All Rights
|
||||
Reserved. You are free to share and adapt this file under the terms of
|
||||
this license:</p>
|
||||
<p>The program should compile with any C compiler, but was tested
|
||||
mostly with gcc on Linux.</p>
|
||||
<p>It doesn’t support 64 bits (due to integer-pointer casts, and <code>a >>31</code>).
|
||||
It does work on 64-bit Linux, because all functions are below 4GB.</p>
|
||||
<h2 id="copyright-and-cc-by-sa-4.0-license">Copyright and CC BY-SA 4.0 License:</h2>
|
||||
<p>This file is Copyright (c) 2023 by Landon Curt Noll. All Rights Reserved.
|
||||
You are free to share and adapt this file under the terms of this license:</p>
|
||||
<pre><code>Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)</code></pre>
|
||||
<p>For more information, see:
|
||||
https://creativecommons.org/licenses/by-sa/4.0/</p>
|
||||
<p>For more information, see: https://creativecommons.org/licenses/by-sa/4.0/</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-index-inventory.sh via bin/md2html.sh -->
|
||||
|
||||
<!-- START: this line starts content generated by: bin/output-index-inventory.sh -->
|
||||
|
||||
<h1 id="inventory-for-2011goren"><a name="inventory"></a>Inventory for
|
||||
2011/goren</h1>
|
||||
<h1 id="inventory-for-2011goren"><a name="inventory"></a>Inventory for 2011/goren</h1>
|
||||
<p><a href="#top">Jump to top</a></p>
|
||||
<h2 id="primary-files">Primary files</h2>
|
||||
<ul>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/goren/goren.c">goren.c</a>
|
||||
- entry source</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/goren/Makefile">Makefile</a>
|
||||
- entry Makefile</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/goren/goren.orig.c">goren.orig.c</a>
|
||||
- original source</li>
|
||||
<li><a href="MagrittePipe.jpg">MagrittePipe.jpg</a> - this is not a
|
||||
pipe</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/goren/try.sh">try.sh</a>
|
||||
- how to run</li>
|
||||
<li><a href="2011_goren.tar.bz2">2011_goren.tar.bz2</a> - download entry
|
||||
source</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/goren/goren.c">goren.c</a> - entry source</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/goren/Makefile">Makefile</a> - entry Makefile</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/goren/goren.orig.c">goren.orig.c</a> - original source</li>
|
||||
<li><a href="MagrittePipe.jpg">MagrittePipe.jpg</a> - this is not a pipe</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/goren/try.sh">try.sh</a> - how to run</li>
|
||||
<li><a href="2011_goren.tar.bz2">2011_goren.tar.bz2</a> - download entry source</li>
|
||||
</ul>
|
||||
<h2 id="secondary-files">Secondary files</h2>
|
||||
<ul>
|
||||
<li><a href="index.html">index.html</a> - entry home page</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/goren/.entry.json">.entry.json</a>
|
||||
- description of entry in JSON</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/goren/.gitignore">.gitignore</a>
|
||||
- list of files that should not be committed under git</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/goren/.entry.json">.entry.json</a> - description of entry in JSON</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/goren/.gitignore">.gitignore</a> - list of files that should not be committed under git</li>
|
||||
<li><a href=".path">.path</a> - directory path from top directory</li>
|
||||
<li><a
|
||||
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/goren/README.md">README.md</a>
|
||||
- markdown source for index.html</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2011/goren/README.md">README.md</a> - markdown source for index.html</li>
|
||||
</ul>
|
||||
|
||||
<!-- END: next line ends content generated by: bin/output-index-inventory.sh -->
|
||||
|
||||
Reference in new issue
Block a user