Merge pull request #2585 from xexyl/fixes-92

Fixes in most of 1992 index.html files
This commit is contained in:
Landon Curt Noll authored and GitHub committed 2024-07-21 00:17:12 -07:00
commit 08104ca043
6 files changed
+30 -20

No files matched your search

+4 -4
View File
@@ -14,9 +14,9 @@
## Judges' remarks: ## Judges' remarks:
The object is to refill the table with 5's, by incrementing or decrementing The object is to refill the table with `5`s, by incrementing or decrementing
numbers as needed. It is the side effects that get you into trouble. If you numbers as needed. It is the side effects that get you into trouble. If you
are not careful, you may find things "at 6's and 7's". :-) are not careful, you may find things "at `6`s and `7`s". :-)
NOTE: Some compilers have had trouble optimizing this entry. NOTE: Some compilers have had trouble optimizing this entry.
@@ -31,8 +31,8 @@ avoids this problem.
## Author's remarks: ## Author's remarks:
It starts off by creating a table with number 5 in all places. The CPU melts It starts off by creating a table with the number `5` in all places. The CPU melts
the numbers and you must return them in original state. When you increase a the numbers and you must return them to the original state. When you increase a
number, all the other eight numbers next to it decrease and vice-versa. number, all the other eight numbers next to it decrease and vice-versa.
+4 -4
View File
@@ -412,9 +412,9 @@ Location: <a href="../../location.html#IT">IT</a> - <em>Italian Republic</em> (<
<h2 id="to-use">To use:</h2> <h2 id="to-use">To use:</h2>
<pre><code> ./marangon</code></pre> <pre><code> ./marangon</code></pre>
<h2 id="judges-remarks">Judges’ remarks:</h2> <h2 id="judges-remarks">Judges’ remarks:</h2>
<p>The object is to refill the table with 5’s, by incrementing or decrementing <p>The object is to refill the table with <code>5</code>s, by incrementing or decrementing
numbers as needed. It is the side effects that get you into trouble. If you numbers as needed. It is the side effects that get you into trouble. If you
are not careful, you may find things “at 6’s and 7’s”. :-)</p> are not careful, you may find things “at <code>6</code>s and <code>7</code>s”. :-)</p>
<p>NOTE: Some compilers have had trouble optimizing this entry.</p> <p>NOTE: Some compilers have had trouble optimizing this entry.</p>
<p>NOTE: Some systems need to compile with <code>-ltermcap</code> as well as <code>-lcurses</code>.</p> <p>NOTE: Some systems need to compile with <code>-ltermcap</code> as well as <code>-lcurses</code>.</p>
<p>NOTE: The original winning source <p>NOTE: The original winning source
@@ -423,8 +423,8 @@ are not careful, you may find things “at 6’s and 7’s”. :-)</p>
returns a <code>void</code>. The file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/marangon/marangon.c">marangon.c</a> returns a <code>void</code>. The file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1992/marangon/marangon.c">marangon.c</a>
avoids this problem.</p> avoids this problem.</p>
<h2 id="authors-remarks">Author’s remarks:</h2> <h2 id="authors-remarks">Author’s remarks:</h2>
<p>It starts off by creating a table with number 5 in all places. The CPU melts <p>It starts off by creating a table with the number <code>5</code> in all places. The CPU melts
the numbers and you must return them in original state. When you increase a the numbers and you must return them to the original state. When you increase a
number, all the other eight numbers next to it decrease and vice-versa.</p> number, all the other eight numbers next to it decrease and vice-versa.</p>
<!-- <!--
+11 -2
View File
@@ -109,11 +109,19 @@ ply of 3). A ply of 3 is in general good enough to avoid not only flaming
blunders but also immediately stupid moves altogether. A ply of 4 will find all blunders but also immediately stupid moves altogether. A ply of 4 will find all
mate-in-two's. mate-in-two's.
### NOTICE to those who wish for a greater challenge:
**If you want a greater challenge, don't read any further**:
just try to understand the program via the source.
If you get stuck, come back and read below for additional hints and information.
### Obfuscation ### Obfuscation
This program is obfuscated in a number of ways. First, it abuses the This program is obfuscated in a number of ways. First, it abuses the
contest rule regarding ';', '{', and '}' in the source not counting contest rule regarding `;`, `{`, and `}` in the source not counting
against the non-whitespace character limit if followed by whitespace. against the non-whitespace character limit if followed by whitespace.
As can be seen from the build file, certain combinations of these As can be seen from the build file, certain combinations of these
characters followed by a particular whitespace character are expanded characters followed by a particular whitespace character are expanded
@@ -154,7 +162,8 @@ Finally, there are three key constants that occur throughout the program: `64`,
which provides a hint as to what the program is up to, they are computed which provides a hint as to what the program is up to, they are computed
probabilistically at run-time. An instance of the ["Inspection probabilistically at run-time. An instance of the ["Inspection
Paradox"](https://en.wikipedia.org/wiki/Renewal_theory#Inspection_paradox) is Paradox"](https://en.wikipedia.org/wiki/Renewal_theory#Inspection_paradox) is
used which happens to produce a value that on average is close to `.64`. used which happens to produce a value that on average is close to `64`.
`10000` instances of this value are computed, added up, and then divided by `10000` instances of this value are computed, added up, and then divided by
`100`. Sometimes the value produced will be `63` or `65` instead of `64` (but `100`. Sometimes the value produced will be `63` or `65` instead of `64` (but
I've never observed any other values), so the result is then rounded to the I've never observed any other values), so the result is then rounded to the
+7 -3
View File
@@ -484,9 +484,13 @@ a little under 4 CPU minutes (and for <code>PK4</code> comes up with the same re
ply of 3). A ply of 3 is in general good enough to avoid not only flaming ply of 3). A ply of 3 is in general good enough to avoid not only flaming
blunders but also immediately stupid moves altogether. A ply of 4 will find all blunders but also immediately stupid moves altogether. A ply of 4 will find all
mate-in-two’s.</p> mate-in-two’s.</p>
<h3 id="notice-to-those-who-wish-for-a-greater-challenge">NOTICE to those who wish for a greater challenge:</h3>
<p><strong>If you want a greater challenge, don’t read any further</strong>:
just try to understand the program via the source.</p>
<p>If you get stuck, come back and read below for additional hints and information.</p>
<h3 id="obfuscation">Obfuscation</h3> <h3 id="obfuscation">Obfuscation</h3>
<p>This program is obfuscated in a number of ways. First, it abuses the <p>This program is obfuscated in a number of ways. First, it abuses the
contest rule regarding ‘;’, ‘{’, and ‘}’ in the source not counting contest rule regarding <code>;</code>, <code>{</code>, and <code>}</code> in the source not counting
against the non-whitespace character limit if followed by whitespace. against the non-whitespace character limit if followed by whitespace.
As can be seen from the build file, certain combinations of these As can be seen from the build file, certain combinations of these
characters followed by a particular whitespace character are expanded characters followed by a particular whitespace character are expanded
@@ -519,8 +523,8 @@ tactic somewhat obfuscates the algorithm used by the program.</p>
which provides a hint as to what the program is up to, they are computed which provides a hint as to what the program is up to, they are computed
probabilistically at run-time. An instance of the <a href="https://en.wikipedia.org/wiki/Renewal_theory#Inspection_paradox">“Inspection probabilistically at run-time. An instance of the <a href="https://en.wikipedia.org/wiki/Renewal_theory#Inspection_paradox">“Inspection
Paradox”</a> is Paradox”</a> is
used which happens to produce a value that on average is close to <code>.64</code>. used which happens to produce a value that on average is close to <code>64</code>.</p>
<code>10000</code> instances of this value are computed, added up, and then divided by <p><code>10000</code> instances of this value are computed, added up, and then divided by
<code>100</code>. Sometimes the value produced will be <code>63</code> or <code>65</code> instead of <code>64</code> (but <code>100</code>. Sometimes the value produced will be <code>63</code> or <code>65</code> instead of <code>64</code> (but
I’ve never observed any other values), so the result is then rounded to the I’ve never observed any other values), so the result is then rounded to the
nearest multiple of <code>4</code>, and then the other constants are derived from it.</p> nearest multiple of <code>4</code>, and then the other constants are derived from it.</p>
+2 -4
View File
@@ -12,8 +12,7 @@ There are two alternate versions that relate to the US specifically. See
The current status of this entry is: The current status of this entry is:
> **STATUS: INABIAF - please DO NOT fix**<br> > **STATUS: INABIAF - please DO NOT fix**
> **STATUS: known bug - please help us fix**
For more detailed information see [1992/westley in bugs.html](../../bugs.html#1992_westley). For more detailed information see [1992/westley in bugs.html](../../bugs.html#1992_westley).
@@ -66,8 +65,7 @@ is functionally equivalent to the first. The original limitation where one has
to have a terminal that wraps at 80 columns is unfortunately in this version to have a terminal that wraps at 80 columns is unfortunately in this version
because it requires a specific length so if you do not have this it will not because it requires a specific length so if you do not have this it will not
look right; use the first alternate version if you want to see correct output look right; use the first alternate version if you want to see correct output
with wider terminals. with wider terminals. To compile the second alternate version:
``` <!---sh--> ``` <!---sh-->
make alt2 make alt2
+2 -3
View File
@@ -414,8 +414,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
<h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3> <h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
<p>The current status of this entry is:</p> <p>The current status of this entry is:</p>
<blockquote> <blockquote>
<p><strong>STATUS: INABIAF - please DO NOT fix</strong><br> <p><strong>STATUS: INABIAF - please DO NOT fix</strong></p>
<strong>STATUS: known bug - please help us fix</strong></p>
</blockquote> </blockquote>
<p>For more detailed information see <a href="../../bugs.html#1992_westley">1992/westley in bugs.html</a>.</p> <p>For more detailed information see <a href="../../bugs.html#1992_westley">1992/westley in bugs.html</a>.</p>
<h2 id="to-use">To use:</h2> <h2 id="to-use">To use:</h2>
@@ -445,7 +444,7 @@ is functionally equivalent to the first. The original limitation where one has
to have a terminal that wraps at 80 columns is unfortunately in this version to have a terminal that wraps at 80 columns is unfortunately in this version
because it requires a specific length so if you do not have this it will not because it requires a specific length so if you do not have this it will not
look right; use the first alternate version if you want to see correct output look right; use the first alternate version if you want to see correct output
with wider terminals.</p> with wider terminals. To compile the second alternate version:</p>
<pre><code> make alt2</code></pre> <pre><code> make alt2</code></pre>
<h3 id="alternate-use">Alternate use:</h3> <h3 id="alternate-use">Alternate use:</h3>
<pre><code> ./whereami.alt.sh lat long</code></pre> <pre><code> ./whereami.alt.sh lat long</code></pre>