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

Fixes in entries of 1994

Browse Source 
The manifest was updated for 1994/tvr. Rebuilt .entry.json and
index.html.

Bug status changed in 1994/tvr as well. The judges noted that it has an
incorrect result in some cases but the author actually noted this as a
feature so it should not be fixed. Other fixes/updates were made in the
bugs file as well.

A number of other entries of 1994 had minor fixes (formatting, links and
similar things).
This commit is contained in:
Cody Boone Ferguson committed 2024-07-24 12:03:57 -07:00
1 parent caf1f6c836
commit 9fdeaf1098
13 files changed
+252 -223
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

1994/imc/README.md
+5 -5
View File
@@ -8,10 +8,10 @@
## To use:
``` <!---sh-->
./imc [NUMBER]
./imc number
```
where `[NUMBER]` is an optional number. Default is 5.
where `number` is an optional number. Default is 5.
## Try:
@@ -69,9 +69,9 @@ useful the exclusive-or operator was while writing function `s()`.
Here are the descriptions of the functions in the library:
> o(n,a,q,d): makes a magic square of order n when n is odd and at least 3.<br>
> s(n,a,q,d): makes a magic square of order n when n equals 4.<br>
> e(n,a,q,d): makes a magic square of order n when n is even and at least 6.
> `o(n,a,q,d)`: makes a magic square of order `n` when `n` is odd and at least 3.<br>
> `s(n,a,q,d)`: makes a magic square of order `n` when `n` equals 4.<br>
> `e(n,a,q,d)`: makes a magic square of order `n` when `n` is even and at least 6.
In the above, `a` (of type `int *`) points to an area of memory in which
the magic square will be stored and `q` (also of type `int *`) points to
1994/imc/index.html
+5 -5
View File
@@ -410,8 +410,8 @@ Location: <a href="../../location.html#GB">GB</a> - <em>United Kingdom of Great
<h2 id="to-build">To build:</h2>
<pre><code> make all</code></pre>
<h2 id="to-use">To use:</h2>
<pre><code> ./imc [NUMBER]</code></pre>
<p>where <code>[NUMBER]</code> is an optional number. Default is 5.</p>
<pre><code> ./imc number</code></pre>
<p>where <code>number</code> is an optional number. Default is 5.</p>
<h2 id="try">Try:</h2>
<pre><code> ./try.sh</code></pre>
<h2 id="judges-remarks">Judges’ remarks:</h2>
@@ -447,9 +447,9 @@ in obfuscated code! :-) Incidentally, I was surprised to find out how
useful the exclusive-or operator was while writing function <code>s()</code>.</p>
<p>Here are the descriptions of the functions in the library:</p>
<blockquote>
<p>o(n,a,q,d): makes a magic square of order n when n is odd and at least 3.<br>
s(n,a,q,d): makes a magic square of order n when n equals 4.<br>
e(n,a,q,d): makes a magic square of order n when n is even and at least 6.</p>
<p><code>o(n,a,q,d)</code>: makes a magic square of order <code>n</code> when <code>n</code> is odd and at least 3.<br>
<code>s(n,a,q,d)</code>: makes a magic square of order <code>n</code> when <code>n</code> equals 4.<br>
<code>e(n,a,q,d)</code>: makes a magic square of order <code>n</code> when <code>n</code> is even and at least 6.</p>
</blockquote>
<p>In the above, <code>a</code> (of type <code>int *</code>) points to an area of memory in which
the magic square will be stored and <code>q</code> (also of type <code>int *</code>) points to
1994/schnitzi/README.md
+12 -7
View File
@@ -5,8 +5,8 @@
```
There are two alternate versions, one that has an increased buffer size and one
that uses `fgets()`; neither are completely functional.
See below section bugs and (mis)features for details and the [alternate
that uses `fgets()`; neither are completely functional. See below section [Bugs
and (mis)features](#bugs-and-misfeatures) for details and the [Alternate
code](#alternate-code) section for how to use.
@@ -35,14 +35,19 @@ For more detailed information see [1994/schnitzi in bugs.html](../../bugs.html#1
## Alternate code:
These alternate versions are for those who wish to help with getting the entry
to use `fgets(3)`. See the
FAQ on "[gets and fgets](../../faq.html#gets)"
for why this is desired.
The first version, `schnitzi.alt.c`, uses `fgets(3)` but when fed its own code
it will generate code that still uses `gets(3)`. What's more is it will not
compile. Other functionality works fine.
it will generate code that still uses `gets(3)`. What's more that code will not
compile. Other functionality of the alt version works fine.
The second version, `schnitzi.alt2.c`, has an increased buffer size but when fed
its own source code it will generate code that can compile but with the original
buffer size. This is due to a comment which is explained in more detail in
[1994/schnitzi in bugs.html](../../bugs.html#1994_schnitzi).
its own source code it will generate code that, although it can compile but, it
has the original buffer size. This is due to a comment which is explained in
more detail in [1994/schnitzi in bugs.html](../../bugs.html#1994_schnitzi).
### Alternate build:
1994/schnitzi/index.html
+11 -7
View File
@@ -410,8 +410,8 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
<h2 id="to-build">To build:</h2>
<pre><code> make all</code></pre>
<p>There are two alternate versions, one that has an increased buffer size and one
that uses <code>fgets()</code>; neither are completely functional.
See below section bugs and (mis)features for details and the <a href="#alternate-code">alternate
that uses <code>fgets()</code>; neither are completely functional. See below section <a href="#bugs-and-misfeatures">Bugs
and (mis)features</a> for details and the <a href="#alternate-code">Alternate
code</a> section for how to use.</p>
<h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
<p>The current status of this entry is:</p>
@@ -424,13 +424,17 @@ code</a> section for how to use.</p>
<h2 id="try">Try:</h2>
<pre><code> ./try.sh</code></pre>
<h2 id="alternate-code">Alternate code:</h2>
<p>These alternate versions are for those who wish to help with getting the entry
to use <code>fgets(3)</code>. See the
FAQ on “<a href="../../faq.html#gets">gets and fgets</a>”
for why this is desired.</p>
<p>The first version, <code>schnitzi.alt.c</code>, uses <code>fgets(3)</code> but when fed its own code
it will generate code that still uses <code>gets(3)</code>. What’s more is it will not
compile. Other functionality works fine.</p>
it will generate code that still uses <code>gets(3)</code>. What’s more that code will not
compile. Other functionality of the alt version works fine.</p>
<p>The second version, <code>schnitzi.alt2.c</code>, has an increased buffer size but when fed
its own source code it will generate code that can compile but with the original
buffer size. This is due to a comment which is explained in more detail in
<a href="../../bugs.html#1994_schnitzi">1994/schnitzi in bugs.html</a>.</p>
its own source code it will generate code that, although it can compile but, it
has the original buffer size. This is due to a comment which is explained in
more detail in <a href="../../bugs.html#1994_schnitzi">1994/schnitzi in bugs.html</a>.</p>
<h3 id="alternate-build">Alternate build:</h3>
<pre><code> make alt</code></pre>
<h3 id="alternate-use">Alternate use:</h3>
1994/shapiro/README.md
+16 -10
View File
@@ -9,8 +9,8 @@
The current status of this entry is:
> **STATUS: missing file - please provide it**<br>
> **STATUS: INABIAF - please DO NOT fix**
> **STATUS: INABIAF - please DO NOT fix**<br>
> **STATUS: missing file - please provide it**
For more detailed information see [1994/shapiro in bugs.html](../../bugs.html#1994_shapiro).
@@ -48,10 +48,11 @@ source file is self documenting. :-)
From time to time, run `ps(1)` and look at the new processes.
See [shapiro.html](shapiro.html) for more information in the internals of this program.
The file `shapiro.alt.c` contains a non-obfuscated version of
this program. Note that this alt file is currently missing. See
[1994/shapiro in bugs.html](../../bugs.html#1994_shapiro) for details.
If you want more information on the internals of this program, see
[shapiro.html](shapiro.html).
The missing file `shapiro.alt.c` is an unobfuscated version of this program. See
[1994/shapiro in bugs.html](../../bugs.html#1994_shapiro).
## Author's remarks:
@@ -59,10 +60,15 @@ this program. Note that this alt file is currently missing. See
The basic theme (pun) of this program is:
```
"This time (everything) is not where it should be."
~~~~
```
> "This **time** (everything) is not where it should be."
### 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.
My entry, [shapiro.c](%%REPO_URL%%/1994/shapiro/shapiro.c), is mostly comments, formatted in the shape of a
1994/shapiro/index.html
+13 -8
View File
@@ -412,8 +412,8 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
<h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
<p>The current status of this entry is:</p>
<blockquote>
<p><strong>STATUS: missing file - please provide it</strong><br>
<strong>STATUS: INABIAF - please DO NOT fix</strong></p>
<p><strong>STATUS: INABIAF - please DO NOT fix</strong><br>
<strong>STATUS: missing file - please provide it</strong></p>
</blockquote>
<p>For more detailed information see <a href="../../bugs.html#1994_shapiro">1994/shapiro in bugs.html</a>.</p>
<h2 id="to-use">To use:</h2>
@@ -434,14 +434,19 @@ bring it back to the foreground.</p>
<p>This entry has many different levels of obfuscation, and yet the
source file is self documenting. :-)</p>
<p>From time to time, run <code>ps(1)</code> and look at the new processes.</p>
<p>See <a href="shapiro.html">shapiro.html</a> for more information in the internals of this program.
The file <code>shapiro.alt.c</code> contains a non-obfuscated version of
this program. Note that this alt file is currently missing. See
<a href="../../bugs.html#1994_shapiro">1994/shapiro in bugs.html</a> for details.</p>
<p>If you want more information on the internals of this program, see
<a href="shapiro.html">shapiro.html</a>.</p>
<p>The missing file <code>shapiro.alt.c</code> is an unobfuscated version of this program. See
<a href="../../bugs.html#1994_shapiro">1994/shapiro in bugs.html</a>.</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<p>The basic theme (pun) of this program is:</p>
<pre><code> &quot;This time (everything) is not where it should be.&quot;
~~~~</code></pre>
<blockquote>
<p>“This <strong>time</strong> (everything) is not where it should be.”</p>
</blockquote>
<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>
<p>My entry, <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/shapiro/shapiro.c">shapiro.c</a>, is mostly comments, formatted in the shape of a
clock. If you strip out the comments and look at the code you will
quickly realize that the comments were the important part and that
1994/tvr/.entry.json
+1 -1
View File
@@ -31,7 +31,7 @@
"OK_to_edit" : true,
"display_as" : "c",
"display_via_github" : true,
"entry_text" : "alternate source code"
"entry_text" : "less obfuscated source code"
},
{
"file_path" : "tvr.orig.c",
1994/tvr/README.md
+4 -4
View File
@@ -16,7 +16,7 @@ code](#alternate-code) below.
The current status of this entry is:
> **STATUS: known bug - please help us fix**
> **STATUS: INABIAF - please DO NOT fix**
For more detailed information see [1994/tvr in bugs.html](../../bugs.html#1994_tvr).
@@ -47,11 +47,11 @@ just try to understand the program without looking at the Alternate code.
If you get stuck, come back and look at the Alternate code.
The author provided us a less obfuscated version that might be of interest to some.
### Alternate build:
The author provided us a less obfuscated version that might be of interest to some.
``` <!---sh-->
make alt
```
@@ -152,7 +152,7 @@ and may confuse paging algorithms easily). This means that for 512x512 windows
you will need 4M of memory.
### `colormapfile`
#### colormapfile
This is the file from which program reads colors for screen `colormap`. The
first line of the file must be a number between `3..254`. This informs the
1994/tvr/index.html
+4 -4
View File
@@ -417,7 +417,7 @@ code</a> below.</p>
<h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
<p>The current status of this entry is:</p>
<blockquote>
<p><strong>STATUS: known bug - please help us fix</strong></p>
<p><strong>STATUS: INABIAF - please DO NOT fix</strong></p>
</blockquote>
<p>For more detailed information see <a href="../../bugs.html#1994_tvr">1994/tvr in bugs.html</a>.</p>
<h2 id="to-use">To use:</h2>
@@ -431,8 +431,8 @@ code</a> below.</p>
<p><strong>If you want a greater challenge, don’t read any further</strong>:
just try to understand the program without looking at the Alternate code.</p>
<p>If you get stuck, come back and look at the Alternate code.</p>
<h3 id="alternate-build">Alternate build:</h3>
<p>The author provided us a less obfuscated version that might be of interest to some.</p>
<h3 id="alternate-build">Alternate build:</h3>
<pre><code> make alt</code></pre>
<h3 id="alternate-use">Alternate use:</h3>
<pre><code> ./tvr.alt altmode screensize/2 &lt; colormapfile</code></pre>
@@ -497,7 +497,7 @@ parameter as shown above.</p>
main memory or the machine will swap heavily (memory references are quite random
and may confuse paging algorithms easily). This means that for 512x512 windows
you will need 4M of memory.</p>
<h3 id="colormapfile"><code>colormapfile</code></h3>
<h4 id="colormapfile">colormapfile</h4>
<p>This is the file from which program reads colors for screen <code>colormap</code>. The
first line of the file must be a number between <code>3..254</code>. This informs the
program how many colors there are to be expected. This is also the maximum
@@ -600,7 +600,7 @@ mono).</li>
<ul>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/tvr/tvr.c">tvr.c</a> - entry source code</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/tvr/Makefile">Makefile</a> - entry Makefile</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/tvr/tvr.alt.c">tvr.alt.c</a> - alternate source code</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/tvr/tvr.alt.c">tvr.alt.c</a> - less obfuscated source code</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/tvr/tvr.orig.c">tvr.orig.c</a> - original source code</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/tvr/try.alt.bw.sh">try.alt.bw.sh</a> - script to try alternate code in black and white mode</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/tvr/try.alt.color.sh">try.alt.color.sh</a> - script to try alternate code in colour mode</li>
1994/weisberg/README.md
+8 -7
View File
@@ -4,8 +4,8 @@
make all
```
There is an alternate version that uses more memory. See [alternate
code](#alternate-code) below for more details.
There is an alternate build (same code, alternate build) that uses more memory.
See [Alternate code](#alternate-code) below for more details.
## To use:
@@ -27,15 +27,16 @@ If you have `primes(1)` installed you might also wish to try:
./primes.sh number
```
where `number` is a positive number, defaulting to 15. The [try.sh](%%REPO_URL%%/1994/weisberg/try.sh)
script will also do this.
where `number` is a positive number, defaulting to 15. The
[try.sh](%%REPO_URL%%/1994/weisberg/try.sh) script will also `try` :-) and do
this.
## Alternate code:
If you liked what you saw from the above program, and happen to
have some 512 Megabytes of virtual memory lying around with to do
something with you might try this version.
have some 512 megabytes of virtual memory lying around with to do
something with you might try this build.
### Alternate build:
@@ -77,7 +78,7 @@ event of a system shutdown or reboot.
### Bugs
The alternative version ([weisberg.c](%%REPO_URL%%/1994/weisberg/weisberg.c)
The alternative build ([weisberg.c](%%REPO_URL%%/1994/weisberg/weisberg.c)
compiled to `weisberg.alt`) has never actually run
to completion. After running for close to a week it had reached somewhere around
250e6, when it became necessary to test the reboot feature (which worked
1994/weisberg/index.html
+8 -7
View File
@@ -409,20 +409,21 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
<!-- BEFORE: 1st line of markdown file: 1994/weisberg/README.md -->
<h2 id="to-build">To build:</h2>
<pre><code> make all</code></pre>
<p>There is an alternate version that uses more memory. See <a href="#alternate-code">alternate
code</a> below for more details.</p>
<p>There is an alternate build (same code, alternate build) that uses more memory.
See <a href="#alternate-code">Alternate code</a> below for more details.</p>
<h2 id="to-use">To use:</h2>
<pre><code> ./weisberg</code></pre>
<h2 id="try">Try:</h2>
<pre><code> ./try.sh</code></pre>
<p>If you have <code>primes(1)</code> installed you might also wish to try:</p>
<pre><code> ./primes.sh number</code></pre>
<p>where <code>number</code> is a positive number, defaulting to 15. The <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/weisberg/try.sh">try.sh</a>
script will also do this.</p>
<p>where <code>number</code> is a positive number, defaulting to 15. The
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/weisberg/try.sh">try.sh</a> script will also <code>try</code> :-) and do
this.</p>
<h2 id="alternate-code">Alternate code:</h2>
<p>If you liked what you saw from the above program, and happen to
have some 512 Megabytes of virtual memory lying around with to do
something with you might try this version.</p>
have some 512 megabytes of virtual memory lying around with to do
something with you might try this build.</p>
<h3 id="alternate-build">Alternate build:</h3>
<pre><code> make alt</code></pre>
<h3 id="alternate-use">Alternate use:</h3>
@@ -443,7 +444,7 @@ run to completion, so as an added feature, it will cease execution upon
reception of a signal (any will do equally well), as well as in the
event of a system shutdown or reboot.</p>
<h3 id="bugs">Bugs</h3>
<p>The alternative version (<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/weisberg/weisberg.c">weisberg.c</a>
<p>The alternative build (<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1994/weisberg/weisberg.c">weisberg.c</a>
compiled to <code>weisberg.alt</code>) has never actually run
to completion. After running for close to a week it had reached somewhere around
250e6, when it became necessary to test the reboot feature (which worked