add rules, guidelines, fix HTML code, move compressed tarball in inventory
By changing the _inventory_order_ of the compressed tarball from
**100000** to **1415926535**, the compressed tarball will land at
the top of the secondary file list and remain still easy to find.
Updated the `manifest.numbers` spreadsheet and rebuilt
the `.entry.json` files.
Added `next/` directory to hold the next IOCCC rules and guidelines.
Added `next/README.md` that `bin/gen-top-html.sh` uses to form
the `next/index.html` file.
Added _Rules and Guidelines_ link to the sidenav bar to link to the
`next/index.html` file.
Added _IOCCC Rules_ as `next/rules.md` that `bin/gen-top-html.sh`
uses to form the `next/rules.html` file.
Added _IOCCC Guidelines_ as `next/guidelines.md` that `bin/gen-top-html.sh`
uses to form the `next/guidelines.html` file.
Changed `bin/gen-top-html.sh` VERSION from "1.2.4 2024-04-13"
to "1.3 2024-04-14".
Prevent `pandoc(1)` from interpreting the commented out language
of a markdown code block as a code class. So a markdown such as:
````
``` <!---sh-->
...
```
````
that produced HTML of the form:
```html
<pre class="<!---sh-->"><code>...</code></pre>
```
will now produce HTML of the form:
```html
<pre><code>...</code></pre>
```
NOTE: Before when the language of a markdown code block
was not commented, the HTML produced by `pandoc(1)` was
oddly indented with extra whitespace on the first line
of the code block. While commenting out the language
of the code block removed some of the odd intending,
it left a weird class in the HTML pre block that
surrounded the HTML code block. This hack prevents
`pandoc(1)` from assigning a class to the HTML pre block.
Changed `in/md2html.sh` VERSION from "1.2.1 2024-04-13"
to "1.3 2024-04-14".
Added `make gen_sitemap` to end of both `make www` and `make
quick_www` in top level Makefile.
Ram `make www` to test under macOS and to perform the above.
**IMPORTANT NOTE**: The current `next/rules.md` and `next/guidelines.md`
are simply the 2020 IOCCC Rules and Guidelines converted into
markdown form. There are **NOT** the Rules and Guidelines that
will be used the IOCCC MOCK, nor the next IOCCC.
TODO: Improve the `bin/gen-status.sh` tool to modify the top of the
`next/rules.md` and `next/guidelines.md` files to keep them
in sync with the _contest_status_ as found in `status.json`.
TODO: Improve the look and feel of the `next/rules.md` and
`next/guidelines.md` markdown files.
This commit is contained in:
Landon Curt Noll committed
1 parent
a672335d2d
commit
518a6336d0
734 files changed
+7919
-4119
No files matched your search
@@ -59,7 +59,7 @@
|
||||
},
|
||||
{
|
||||
"file_path" : "1994_westley.tar.bz2",
|
||||
"inventory_order" : 100000,
|
||||
"inventory_order" : 1415926535,
|
||||
"OK_to_edit" : false,
|
||||
"display_as" : "tbz2",
|
||||
"display_via_github" : false,
|
||||
|
||||
+13
-12
@@ -88,6 +88,7 @@
|
||||
<div class="sidenav">
|
||||
<a href="../../news.html">IOCCC News</a>
|
||||
<a href="../../status.html">Contest status</a>
|
||||
<a href="../../next/index.html">Rules and Guidelines</a>
|
||||
<a href="../../faq.html#submit">How to enter the IOCCC</a>
|
||||
<a href="../../faq.html">FAQ</a>
|
||||
</div>
|
||||
@@ -141,7 +142,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
|
||||
<!-- START: this line starts content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
|
||||
|
||||
<h2 id="to-build">To build:</h2>
|
||||
<pre class="<!---sh-->"><code> make alt</code></pre>
|
||||
<pre><code> make alt</code></pre>
|
||||
<p>We recommend that you try the alternate version first as the original entry
|
||||
requires (for better display) 80 columns and 8 character tabs with wraparound.</p>
|
||||
<p>The alt code uses the same logic as the original code except that the original
|
||||
@@ -149,7 +150,7 @@ code used <code>#include</code>s of files that do not exist to generate the mess
|
||||
compiler errors) whereas the alt code uses <code>printf(3)</code>. For the original entry
|
||||
see <a href="#original-code">Original code</a> below.</p>
|
||||
<h2 id="to-use">To use:</h2>
|
||||
<pre class="<!---sh-->"><code> ./westley.alt</code></pre>
|
||||
<pre><code> ./westley.alt</code></pre>
|
||||
<p>The purpose of the game is to escape the dungeon. Depending on the compiler line
|
||||
you will get a different message when you run the program. One compiler line
|
||||
will make you win the game (escape the dungeon) and others will show something
|
||||
@@ -164,10 +165,10 @@ from start to finish.</p>
|
||||
<h2 id="try">Try:</h2>
|
||||
<p>For something more interesting try compiling it with different <code>cc -D</code> arguments
|
||||
and then run the program each time. For example:</p>
|
||||
<pre class="<!---sh-->"><code> cc -Describe -Door westley.alt.c -o westley.alt && ./westley.alt
|
||||
<pre><code> cc -Describe -Door westley.alt.c -o westley.alt && ./westley.alt
|
||||
cc -Describe -Drain westley.alt.c -o westley.alt && ./westley.alt</code></pre>
|
||||
<p>To see the game from start to finish, try:</p>
|
||||
<pre class="<!---sh-->"><code> ./try.alt.sh</code></pre>
|
||||
<pre><code> ./try.alt.sh</code></pre>
|
||||
<h2 id="original-code">Original code:</h2>
|
||||
<p>The purpose of the game is to escape the dungeon <strong>via the compiler line
|
||||
where you get <em>messages as compiler errors</em></strong>. Depending on the compiler line you
|
||||
@@ -177,7 +178,7 @@ game!</p>
|
||||
wraparound. The alternate code does not have this limitation and it is for this
|
||||
reason that we recommend you try it first.</p>
|
||||
<h3 id="original-build">Original build:</h3>
|
||||
<pre class="<!---sh-->"><code> make all</code></pre>
|
||||
<pre><code> make all</code></pre>
|
||||
<p>There are a variety of different <code>-D</code> flags you can give to <code>cc</code> that change the
|
||||
message you get. You might wish to look at the <a href="westley.c">source code</a> to get a
|
||||
better idea or see below in the <a href="#original-try">Original try</a> section for
|
||||
@@ -196,15 +197,15 @@ error messages; there is no running the program.</p>
|
||||
<h3 id="original-try">Original try:</h3>
|
||||
<p>For something more interesting try compiling it with different <code>cc -D</code>
|
||||
arguments:</p>
|
||||
<pre class="<!---sh-->"><code> cc -Describe -Door westley.c
|
||||
<pre><code> cc -Describe -Door westley.c
|
||||
cc -Describe -Drain westley.c</code></pre>
|
||||
<p>To see the game from start to complete, try:</p>
|
||||
<pre class="<!---sh-->"><code> ./try.sh</code></pre>
|
||||
<pre><code> ./try.sh</code></pre>
|
||||
<h2 id="judges-remarks">Judges’ remarks:</h2>
|
||||
<p>Not all compiler errors are bad.</p>
|
||||
<p>For spoilers see the end of the notes from the author below.</p>
|
||||
<p>To use:</p>
|
||||
<pre class="<!---sh-->"><code> ./try.sh</code></pre>
|
||||
<pre><code> ./try.sh</code></pre>
|
||||
<h2 id="authors-remarks">Author’s remarks:</h2>
|
||||
<p>This program, in accordance with the rules, compiles into a legal
|
||||
C program without human intervention. However, it simply compiles
|
||||
@@ -213,7 +214,7 @@ to actually compile the program.</p>
|
||||
<p>This program is a simple adventure game which uses only C preprocessor
|
||||
error messages (for missing <code>#include</code> files) as output. To begin,
|
||||
try to compile the program with no options:</p>
|
||||
<pre class="<!---sh-->"><code> cc westley.c</code></pre>
|
||||
<pre><code> cc westley.c</code></pre>
|
||||
<p>This will fail, producing an error message for a missing <code>#include</code>
|
||||
file as the opening description. Your terminal should be set for
|
||||
80 columns, 8 character tabs, and wraparound, as there is no way
|
||||
@@ -232,7 +233,7 @@ to reliably output newlines. You should see something like this
|
||||
missing include file name, which functions as the game text.</p>
|
||||
<p>To “do” things, all words must start with <code>-D</code>. For example, to
|
||||
look at the door, do:</p>
|
||||
<pre class="<!---sh-->"><code> cc -Describe -Door prog.c</code></pre>
|
||||
<pre><code> cc -Describe -Door prog.c</code></pre>
|
||||
<p>…and you will get another error message telling you about the door.
|
||||
(note: some compilers will stop after the first missing include file,
|
||||
while others will continue to try compiling; the latter will repeat
|
||||
@@ -241,7 +242,7 @@ with “verbose” turned on).</p>
|
||||
<p>The goal of the game is to escape the dungeon.</p>
|
||||
<p>Here is a walk-through for the game, including a few dead-ends:</p>
|
||||
<h3 id="spoiler">SPOILER</h3>
|
||||
<pre class="<!---sh-->"><code> cc -Describe -Door westley.c
|
||||
<pre><code> cc -Describe -Door westley.c
|
||||
cc -Describe -Drain westley.c
|
||||
cc -Describe -Dwarf westley.c
|
||||
cc -Describe -Debris westley.c # or -Dungeon
|
||||
@@ -291,10 +292,10 @@ unimportant.</p>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/westley.orig.c">westley.orig.c</a> - original source</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/try.alt.sh">try.alt.sh</a> - how to run alternative code</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/try.sh">try.sh</a> - how to run</li>
|
||||
<li><a href="1994_westley.tar.bz2">1994_westley.tar.bz2</a> - download entry tarball</li>
|
||||
</ul>
|
||||
<h2 id="secondary-files">Secondary files</h2>
|
||||
<ul>
|
||||
<li><a href="1994_westley.tar.bz2">1994_westley.tar.bz2</a> - download entry tarball</li>
|
||||
<li><a href="index.html">index.html</a> - this web page</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/README.md">README.md</a> - markdown source for this web page</li>
|
||||
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/westley/.entry.json">.entry.json</a> - description of entry in JSON</li>
|
||||
|
||||
Reference in new issue
Block a user