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

2005/mikeash/index.html
+89 -131
View File
@@ -130,8 +130,8 @@
<h2 id="author"><a name="author"></a>Author:</h2>
<ul>
<li>Name: <a href="../../authors.html#Michael_Ash">Michael Ash</a><br>
Location: <a href="../../location.html#US">US</a> - <em>United States of
America</em> (<em>United States</em>) <br><br></li>
Location: <a href="../../location.html#US">US</a> - <em>United States of America</em> (<em>United States</em>)
<br><br></li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-author.sh -->
@@ -144,173 +144,131 @@ America</em> (<em>United States</em>) <br><br></li>
<h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
<p>The current status of this entry is:</p>
<pre><code>STATUS: INABIAF - please **DO NOT** fix</code></pre>
<p>For more detailed information see <a
href="../../bugs.html#2005_mikeash">2005 mikeash bugs</a>.</p>
<p>For more detailed information see <a href="../../bugs.html#2005_mikeash">2005 mikeash bugs</a>.</p>
<h2 id="to-use">To use:</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">./mikeash</span></span></code></pre></div>
<p>NOTE: the author stated that they tested this under i386 machines but
this works under 64-bit (x86_64, arm64) machines too.</p>
<p>NOTE: the author stated that they tested this under i386 machines but this works
under 64-bit (x86_64, arm64) machines too.</p>
<h2 id="try">Try:</h2>
<div class="sourceCode" id="cb4"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-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>Having problems speaking code? Do you <a
href="https://en.wikipedia.org/wiki/Lisp_(programming_language)">LISP</a>?
Parenthetically speaking, this entry takes advantage of C99 features,
while speaking parenthetically. Best of all, it self-reproduces!</p>
<p>Having problems speaking code? Do you <a href="https://en.wikipedia.org/wiki/Lisp_(programming_language)">LISP</a>? Parenthetically
speaking, this entry takes advantage of C99 features, while
speaking parenthetically. Best of all, it self-reproduces!</p>
<p>John McCarthy might not have imagined it quite like this! :-)</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<p>This program is a self-reproducing program, which is on the IOCCC’s
list of discouraged program types. Worse, it’s a self-reproducing
program written in <a
href="https://en.wikipedia.org/wiki/Common_Lisp">Common Lisp</a>. What’s
this doing as an entry to the IOCCC?</p>
<p>This program is a self-reproducing program, which is on the IOCCC’s list
of discouraged program types. Worse, it’s a self-reproducing program
written in <a href="https://en.wikipedia.org/wiki/Common_Lisp">Common Lisp</a>. What’s this
doing as an entry to the IOCCC?</p>
<p>Start over: this program, when compiled with a C99 compiler, is an
interpreter for an extremely limited and highly broken subset of <a
href="https://en.wikipedia.org/wiki/Common_Lisp">Common Lisp</a>.</p>
<p>It requires C99 because of <code>C99</code>’s ability to declare
variables in the initializer of a <code>for</code> loop. Unfortunately,
C99 mode typically warns about implicitly declared functions, and
preprocessor directives prevent the program from being valid <a
href="https://en.wikipedia.org/wiki/Common_Lisp">Common Lisp</a>. As a
interpreter for an extremely limited and highly broken subset of <a href="https://en.wikipedia.org/wiki/Common_Lisp">Common
Lisp</a>.</p>
<p>It requires C99 because of <code>C99</code>’s ability to declare variables in the
initializer of a <code>for</code> loop. Unfortunately, C99 mode typically warns about
implicitly declared functions, and preprocessor directives prevent the program
from being valid <a href="https://en.wikipedia.org/wiki/Common_Lisp">Common Lisp</a>. As a
result, several warnings will be printed about implicit declarations of
functions. There are also warnings about unknown escape sequences in the
constant string, due to different string escape semantics in C and Lisp,
and some implicit integer-to-pointer conversions due to the
implicitly-declared functions.</p>
constant string, due to different string escape semantics in C and Lisp, and
some implicit integer-to-pointer conversions due to the implicitly-declared
functions.</p>
<p>Try:</p>
<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">&#39;(format t &quot;~s&quot; (+ 2 2 ))&#39;</span> <span class="kw">|</span> <span class="ex">./mikeash</span></span></code></pre></div>
<p>You should see <code>4"</code> echoed on your command prompt. The
<code>"</code> after the 4 and the lack of a newline are due to the
somewhat broken implementation of the format function. More
sophisticated arithmetic expressions may be used:</p>
<p>You should see <code>4"</code> echoed on your command prompt. The <code>"</code> after the 4 and
the lack of a newline are due to the somewhat broken implementation of
the format function. More sophisticated arithmetic expressions may be
used:</p>
<div class="sourceCode" id="cb6"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb6-1"><a href="#cb6-1" aria-hidden="true" tabindex="-1"></a><span class="bu">echo</span> <span class="st">&#39;(format t &quot;~s&quot; (* (+ 2 2 ) (- 5 (/ 9 3 ))))&#39;</span> <span class="kw">|</span> <span class="ex">./mikeash</span></span></code></pre></div>
<p>This evaluates the expression <code>(2+2) * (5 - 9/3)</code> giving
the correct result, <code>8"</code> (with the same issue of no newline
after the <code>"</code>). Note that due to the highly ad-hoc nature of
the tokenizer, the spaces before the closing parentheses are
mandatory.</p>
<p>The program can also be run in an interactive mode, by simply
executing <code>./mikeash</code> and then typing lisp expressions, but
this is difficult due to the lack of proper editing facilities and the
total lack of error recovery in the interpreter. Typos will most likely
crash the program.</p>
<p>Aside from being required to put spaces between tokens and closing
parentheses, there are other limitations on the dialect of <a
href="https://en.wikipedia.org/wiki/Common_Lisp">Common Lisp</a> that
this program understands:</p>
<p>This evaluates the expression <code>(2+2) * (5 - 9/3)</code> giving the correct result,
<code>8"</code> (with the same issue of no newline after the <code>"</code>). Note that due to the
highly ad-hoc nature of the tokenizer, the spaces before the closing parentheses
are mandatory.</p>
<p>The program can also be run in an interactive mode, by simply executing
<code>./mikeash</code> and then typing lisp expressions, but this is difficult due to the
lack of proper editing facilities and the total lack of error recovery in the
interpreter. Typos will most likely crash the program.</p>
<p>Aside from being required to put spaces between tokens and closing parentheses,
there are other limitations on the dialect of <a href="https://en.wikipedia.org/wiki/Common_Lisp">Common
Lisp</a> that this program understands:</p>
<ul>
<li><p>The only built-in functions are <code>defvar</code>,
<code>format</code>, <code>substitute</code>, <code>char-upcase</code>,
<code>+</code>, <code>-</code>, <code>*</code>, and
<code>/</code>.</p></li>
<li><p>Only one variable is available. This variable is called
<code>q</code>, although any symbol name starting with the letter
<code>q</code> will be mapped to this variable.</p></li>
<li><p>Only the first letter of a function name is significant. For
example, <code>format</code>, <code>f</code>, <code>farm</code>, and
various other words starting with <code>f</code> will all map to the
<code>format</code> function.</p></li>
<li><p>The <code>defvar</code> function completely ignores its first
parameter. It will always store the result of evaluating its second
parameter in <code>q</code>. Unlike in <a
href="https://en.wikipedia.org/wiki/Common_Lisp">Common Lisp</a>,
multiple invocations of <code>defvar</code> on the same variable will
overwrite old values.</p></li>
<li><p>Character constants are limited to <code>#\Newline</code> and
single-character constants such as <code>#\x</code>.</p></li>
<li><p>The <code>char-upcase</code> function will give strange results
if passed something other than a lowercase character.</p></li>
<li><p>The <code>format</code> function takes exactly three parameters.
The first parameter is ignored; output always goes to
<code>stdout</code>. The second parameter must have exactly one
<code>~s</code> format specifier in it, and no other format specifiers
are permitted.</p></li>
<li><p>The only built-in functions are <code>defvar</code>, <code>format</code>, <code>substitute</code>,
<code>char-upcase</code>, <code>+</code>, <code>-</code>, <code>*</code>, and <code>/</code>.</p></li>
<li><p>Only one variable is available. This variable is called <code>q</code>, although any
symbol name starting with the letter <code>q</code> will be mapped to this variable.</p></li>
<li><p>Only the first letter of a function name is significant. For example,
<code>format</code>, <code>f</code>, <code>farm</code>, and various other words starting with <code>f</code> will all map to
the <code>format</code> function.</p></li>
<li><p>The <code>defvar</code> function completely ignores its first parameter. It will always
store the result of evaluating its second parameter in <code>q</code>. Unlike in <a href="https://en.wikipedia.org/wiki/Common_Lisp">Common
Lisp</a>, multiple invocations of
<code>defvar</code> on the same variable will overwrite old values.</p></li>
<li><p>Character constants are limited to <code>#\Newline</code> and single-character
constants such as <code>#\x</code>.</p></li>
<li><p>The <code>char-upcase</code> function will give strange results if passed something
other than a lowercase character.</p></li>
<li><p>The <code>format</code> function takes exactly three parameters. The first parameter is
ignored; output always goes to <code>stdout</code>. The second parameter must have exactly
one <code>~s</code> format specifier in it, and no other format specifiers are permitted.</p></li>
<li><p>The arithmetic functions take exactly two parameters.</p></li>
<li><p>All tokens must be separated from a following <code>)</code> by
whitespace.</p></li>
<li><p>A lot of other things. Notably, the language which this program
interprets is nowhere near <a
href="https://en.wikipedia.org/wiki/Turing_completeness">Turing-complete</a>.</p></li>
<li><p>All tokens must be separated from a following <code>)</code> by whitespace.</p></li>
<li><p>A lot of other things. Notably, the language which this program interprets is
nowhere near
<a href="https://en.wikipedia.org/wiki/Turing_completeness">Turing-complete</a>.</p></li>
</ul>
<p>Basically, the <a
href="https://en.wikipedia.org/wiki/Lisp_(programming_language)">LISP</a>
interpreter is good for some basic math operations, and for running
itself. To do the latter, try this:</p>
<p>Basically, the <a href="https://en.wikipedia.org/wiki/Lisp_(programming_language)">LISP</a> interpreter is good for some basic math operations, and
for running itself. To do the latter, try this:</p>
<div class="sourceCode" id="cb7"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./mikeash</span> <span class="op">&lt;</span> mikeash.c <span class="op">&gt;</span> mikeash2.c</span>
<span id="cb7-2"><a href="#cb7-2" aria-hidden="true" tabindex="-1"></a><span class="fu">diff</span> mikeash.c mikeash2.c</span></code></pre></div>
<p>The program can also be run from an implementation of <a
href="https://en.wikipedia.org/wiki/Common_Lisp">common lisp</a>. To do
this, run the common lisp compiler and then type the following
command:</p>
<p>The program can also be run from an implementation of <a href="https://en.wikipedia.org/wiki/Common_Lisp">common
lisp</a>. To do
this, run the common lisp compiler and then type the following command:</p>
<pre><code>(load &quot;mikeash.c&quot;)</code></pre>
<p>The source code of <a href="mikeash.c">mikeash.c</a> will be
printed.</p>
<p>The source code of <a href="mikeash.c">mikeash.c</a> will be printed.</p>
<h3 id="obfuscation">Obfuscation</h3>
<p><code>Lispob</code> is obfuscated in several ways. First, it’s
actually two programs in one, which actually share a small amount of
code. Running a C code beautifier will destroy the <a
href="https://en.wikipedia.org/wiki/Lisp_(programming_language)">LISP</a>
program contained within. Second and more importantly, it is very badly
written, which will presumably confuse people who are used to looking at
well-implemented interpreters.</p>
<p>The program comes in at just under 2k of significant characters.
However, this size is exaggerated, because it contains a complete copy
of itself for the self-reproducing <a
href="https://en.wikipedia.org/wiki/Turing_completeness">LISP</a>
program, making it twice the size. This doubling effect made it
something of a challenge to fit inside the IOCCC’s size limit.</p>
<p><code>Lispob</code> is obfuscated in several ways. First, it’s actually two programs
in one, which actually share a small amount of code. Running a C code
beautifier will destroy the <a href="https://en.wikipedia.org/wiki/Lisp_(programming_language)">LISP</a> program contained within. Second and
more importantly, it is very badly written, which will presumably
confuse people who are used to looking at well-implemented interpreters.</p>
<p>The program comes in at just under 2k of significant characters. However, this
size is exaggerated, because it contains a complete copy of itself for the
self-reproducing <a href="https://en.wikipedia.org/wiki/Turing_completeness">LISP</a>
program, making it twice the size. This doubling effect made it something of a
challenge to fit inside the IOCCC’s size limit.</p>
<p>This code should be highly portable. It was tested under Mac OS X and
Linux on i386, but it should run elsewhere. It requires ASCII due to
hardcoding various character constants. Other than this requirement, it
should run anywhere there’s a conforming C99 compiler and a standard C
library.</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>
should run anywhere there’s a conforming C99 compiler and a standard
C library.</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-2005mikeash"><a name="inventory"></a>Inventory for
2005/mikeash</h1>
<h1 id="inventory-for-2005mikeash"><a name="inventory"></a>Inventory for 2005/mikeash</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/2005/mikeash/mikeash.c">mikeash.c</a>
- entry source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/mikeash/Makefile">Makefile</a>
- entry Makefile</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/mikeash/mikeash.orig.c">mikeash.orig.c</a>
- original source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/mikeash/try.sh">try.sh</a>
- how to run</li>
<li><a href="2005_mikeash.tar.bz2">2005_mikeash.tar.bz2</a> - download
entry source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/mikeash/mikeash.c">mikeash.c</a> - entry source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/mikeash/Makefile">Makefile</a> - entry Makefile</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/mikeash/mikeash.orig.c">mikeash.orig.c</a> - original source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/mikeash/try.sh">try.sh</a> - how to run</li>
<li><a href="2005_mikeash.tar.bz2">2005_mikeash.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/2005/mikeash/.entry.json">.entry.json</a>
- description of entry in JSON</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/mikeash/.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/2005/mikeash/.entry.json">.entry.json</a> - description of entry in JSON</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/mikeash/.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/2005/mikeash/README.md">README.md</a>
- markdown source for index.html</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2005/mikeash/README.md">README.md</a> - markdown source for index.html</li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-inventory.sh -->