fix many internal links

Fixed a number of internal links that need to
go to the GitHub site.

Ran `make www` to perform the above.
This commit is contained in:
Landon Curt Noll committed 2024-04-24 02:37:42 -07:00
1 parent b84f8cbe28
commit e7d69bc232
175 files changed
+645 -631

No files matched your search

+1 -1
View File
@@ -104,7 +104,7 @@ of operators, and control constructs.
The compiler has absolutely no error checking, so things
can go wrong. But this is what seasoned C programmers are used to.
Assume that the interpreter has been compiled (source in [august.c](august.c)
Assume that the interpreter has been compiled (source in [august.c](%%REPO_URL%%/1996/august/august.c)
and binary in august) and that we have this in a file named `test.oc`:
``` <!---c-->
+1 -1
View File
@@ -429,7 +429,7 @@ syntax). Arrays can only be global. There is a rather limited set
of operators, and control constructs.</p>
<p>The compiler has absolutely no error checking, so things
can go wrong. But this is what seasoned C programmers are used to.</p>
<p>Assume that the interpreter has been compiled (source in <a href="august.c">august.c</a>
<p>Assume that the interpreter has been compiled (source in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/august/august.c">august.c</a>
and binary in august) and that we have this in a file named <code>test.oc</code>:</p>
<pre><code> main() { putchar(&#39;!&#39;); putchar(&#39;\n&#39;); exit(0); }</code></pre>
<p>We can then compile by</p>
+1 -1
View File
@@ -48,7 +48,7 @@ make it easier to see what is happening.
## Judges' remarks:
The original program, with only slight obfuscations, may be found
in [hunni.c](%%REPO_URL%%/1996/schweikh2/hunni.c). The perl script, [hunni.pl](hunni.pl), obfuscates it
in [hunni.c](%%REPO_URL%%/1996/schweikh2/hunni.c). The perl script, [hunni.pl](%%REPO_URL%%/1996/schweikh2/hunni.pl), obfuscates it
appropriately. Try:
``` <!---sh-->
+1 -1
View File
@@ -399,7 +399,7 @@ ctrl-c to stop it. Observe how the <a href="https://github.com/ioccc-src/temp-te
make it easier to see what is happening.</p>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>The original program, with only slight obfuscations, may be found
in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/schweikh2/hunni.c">hunni.c</a>. The perl script, <a href="hunni.pl">hunni.pl</a>, obfuscates it
in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/schweikh2/hunni.c">hunni.c</a>. The perl script, <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/schweikh2/hunni.pl">hunni.pl</a>, obfuscates it
appropriately. Try:</p>
<pre><code> less hunni.c
+1 -1
View File
@@ -131,7 +131,7 @@ situation and effectively halts.
I had the pleasure and pain to find all three behaviours on the
platforms I use regularly.
The file [schweikh3.info](schweikh3.info) has output for
The file [schweikh3.info](%%REPO_URL%%/1996/schweikh3/schweikh3.info) has output for
Solaris, FreeBSD and Linux. The Linux case is interesting in that
the behaviour changes when `calloc(3)` is used instead of `malloc(3)`.
For FreeBSD, the last two lines are not messages stemming from
+1 -1
View File
@@ -463,7 +463,7 @@ situation and effectively halts.</p></li>
</ol>
<p>I had the pleasure and pain to find all three behaviours on the
platforms I use regularly.</p>
<p>The file <a href="schweikh3.info">schweikh3.info</a> has output for
<p>The file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/schweikh3/schweikh3.info">schweikh3.info</a> has output for
Solaris, FreeBSD and Linux. The Linux case is interesting in that
the behaviour changes when <code>calloc(3)</code> is used instead of <code>malloc(3)</code>.
For FreeBSD, the last two lines are not messages stemming from
+2 -2
View File
@@ -60,8 +60,8 @@ This 1-line program allows various analog ASCII clocks to print out the time;
the ASCII clock is built from the command line arguments, so many different
types of clocks can be generated. Three different scripts are supplied to print
out a grandfather clock, a mantle clock that runs backwards, and a linear-style
clock. (they are [clock1.sh](clock1.sh), [clock2.sh](clock2.sh), and
[clock3.sh](clock3.sh))
clock. (they are [clock1.sh](%%REPO_URL%%/1996/westley/clock1.sh), [clock2.sh](%%REPO_URL%%/1996/westley/clock2.sh), and
[clock3.sh](%%REPO_URL%%/1996/westley/clock3.sh))
The program makes the following (possibly non-portable) assumptions:
+2 -2
View File
@@ -406,8 +406,8 @@ understand it.</p>
the ASCII clock is built from the command line arguments, so many different
types of clocks can be generated. Three different scripts are supplied to print
out a grandfather clock, a mantle clock that runs backwards, and a linear-style
clock. (they are <a href="clock1.sh">clock1.sh</a>, <a href="clock2.sh">clock2.sh</a>, and
<a href="clock3.sh">clock3.sh</a>)</p>
clock. (they are <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/westley/clock1.sh">clock1.sh</a>, <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/westley/clock2.sh">clock2.sh</a>, and
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/westley/clock3.sh">clock3.sh</a>)</p>
<p>The program makes the following (possibly non-portable) assumptions:</p>
<ol type="1">
<li><p>Command line strings can be written to.</p></li>