fix internal links in entry index.html from 1984 thru 2012
This commit is contained in:
1 parent
2da0a6c05f
commit
99cd17401e
151 files changed
+360
-360
No files matched your search
@@ -5,7 +5,7 @@
|
||||
```
|
||||
|
||||
The programs that this program is supposed to act on,
|
||||
[anonymous.ten.c](anonymous.ten.c) and [anonymous.bed.c](anonymous.bed.c),
|
||||
[anonymous.ten.c](%%REPO_URL%%/2001/anonymous/anonymous.ten.c) and [anonymous.bed.c](%%REPO_URL%%/2001/anonymous/anonymous.bed.c),
|
||||
compiled with `make`, MUST be compiled as 32-bit ELF binaries. In the case that
|
||||
this fails these programs will be compiled as 64-bit binaries as alternate code,
|
||||
`anonymous.ten.alt` and `anonymous.bed.alt`, ELF or otherwise. However trying to
|
||||
@@ -47,7 +47,7 @@ set to) and run it directly.
|
||||
What happens if the x86 program has already been modified by this program? The
|
||||
judges' remarks below might give you a hint!
|
||||
|
||||
What happens if you try it on another file like [anonymous.c](anonymous.c)? Can
|
||||
What happens if you try it on another file like [anonymous.c](%%REPO_URL%%/2001/anonymous/anonymous.c)? Can
|
||||
you recompile it okay? What if you run it on `anonymous` itself? Can you run the
|
||||
program successfully after it without recompiling?
|
||||
|
||||
@@ -218,10 +218,10 @@ In short, please consider this a full disclaimer for any bug that may
|
||||
turn up - yes the program is unsafe, but it's pretty cool anyway.
|
||||
|
||||
Despite all this, the translator is not exclusively limited to running the
|
||||
[anonymous.ten](anonymous.ten.c) program. Other trivial **_x86_** programs may
|
||||
[anonymous.ten](%%REPO_URL%%/2001/anonymous/anonymous.ten.c) program. Other trivial **_x86_** programs may
|
||||
run on the translator \- and I have successfully run a wide range of "Hello
|
||||
World" programs, including one of last year's IOCCC entries,
|
||||
[tomx](../../2000/tomx/tomx.c).
|
||||
[tomx](2001/anonymous/2000/tomx/tomx.c).
|
||||
|
||||
|
||||
### Complete Program
|
||||
@@ -233,7 +233,7 @@ new set of switches, and the call to `execv(3)` asks for the newly compiled
|
||||
program to be executed. I would point out that almost every other entry to this
|
||||
competition also require a C compiler (well, the published winning entries at any rate,
|
||||
and I recognize that a few don't). There is little real difference between this
|
||||
program and one like last year's entry [dhyang](../../2000/dhyang/dhyang.c); both are
|
||||
program and one like last year's entry [dhyang](%%REPO_URL%%/2000/dhyang/dhyang.c); both are
|
||||
just C programs that generate C code as their output.
|
||||
|
||||
Enjoy and thanks!
|
||||
|
||||
@@ -155,7 +155,7 @@ Location: <a href="../../location.html#GB">GB</a> - <em>United Kingdom of Great
|
||||
<h2 id="to-build">To build:</h2>
|
||||
<pre><code> make</code></pre>
|
||||
<p>The programs that this program is supposed to act on,
|
||||
<a href="anonymous.ten.c">anonymous.ten.c</a> and <a href="anonymous.bed.c">anonymous.bed.c</a>,
|
||||
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/anonymous/anonymous.ten.c">anonymous.ten.c</a> and <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/anonymous/anonymous.bed.c">anonymous.bed.c</a>,
|
||||
compiled with <code>make</code>, MUST be compiled as 32-bit ELF binaries. In the case that
|
||||
this fails these programs will be compiled as 64-bit binaries as alternate code,
|
||||
<code>anonymous.ten.alt</code> and <code>anonymous.bed.alt</code>, ELF or otherwise. However trying to
|
||||
@@ -177,7 +177,7 @@ whatever your system will compile them as).</p>
|
||||
set to) and run it directly.</p>
|
||||
<p>What happens if the x86 program has already been modified by this program? The
|
||||
judges’ remarks below might give you a hint!</p>
|
||||
<p>What happens if you try it on another file like <a href="anonymous.c">anonymous.c</a>? Can
|
||||
<p>What happens if you try it on another file like <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/anonymous/anonymous.c">anonymous.c</a>? Can
|
||||
you recompile it okay? What if you run it on <code>anonymous</code> itself? Can you run the
|
||||
program successfully after it without recompiling?</p>
|
||||
<h2 id="alternate-code">Alternate code:</h2>
|
||||
@@ -295,10 +295,10 @@ can only pass up to 3 parameters to the target library function, etc.</p>
|
||||
<p>In short, please consider this a full disclaimer for any bug that may
|
||||
turn up - yes the program is unsafe, but it’s pretty cool anyway.</p>
|
||||
<p>Despite all this, the translator is not exclusively limited to running the
|
||||
<a href="anonymous.ten.c">anonymous.ten</a> program. Other trivial <strong><em>x86</em></strong> programs may
|
||||
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/anonymous/anonymous.ten.c">anonymous.ten</a> program. Other trivial <strong><em>x86</em></strong> programs may
|
||||
run on the translator - and I have successfully run a wide range of “Hello
|
||||
World” programs, including one of last year’s IOCCC entries,
|
||||
<a href="../../2000/tomx/tomx.c">tomx</a>.</p>
|
||||
<a href="2001/anonymous/2000/tomx/tomx.c">tomx</a>.</p>
|
||||
<h3 id="complete-program">Complete Program</h3>
|
||||
<p>The fact that the program makes calls to <code>system(3)</code> and <code>execv(3)</code> may imply that
|
||||
it is not a complete program in its own right, as it relies on other programs.
|
||||
@@ -307,7 +307,7 @@ new set of switches, and the call to <code>execv(3)</code> asks for the newly co
|
||||
program to be executed. I would point out that almost every other entry to this
|
||||
competition also require a C compiler (well, the published winning entries at any rate,
|
||||
and I recognize that a few don’t). There is little real difference between this
|
||||
program and one like last year’s entry <a href="../../2000/dhyang/dhyang.c">dhyang</a>; both are
|
||||
program and one like last year’s entry <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2000/dhyang/dhyang.c">dhyang</a>; both are
|
||||
just C programs that generate C code as their output.</p>
|
||||
<p>Enjoy and thanks!</p>
|
||||
<!--
|
||||
|
||||
@@ -54,7 +54,7 @@ You can use it by typing:
|
||||
or by giving the C source to its standard input.
|
||||
|
||||
`args` are given to the `main()` function of `bellard.c` (`argv[0]` is
|
||||
[bellard.c](bellard.c)).
|
||||
[bellard.c](%%REPO_URL%%/2001/bellard/bellard.c)).
|
||||
|
||||
|
||||
### Examples:
|
||||
|
||||
@@ -176,7 +176,7 @@ program.</p>
|
||||
<pre><code> ./bellard bellard.c [args]...</code></pre>
|
||||
<p>or by giving the C source to its standard input.</p>
|
||||
<p><code>args</code> are given to the <code>main()</code> function of <code>bellard.c</code> (<code>argv[0]</code> is
|
||||
<a href="bellard.c">bellard.c</a>).</p>
|
||||
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/bellard/bellard.c">bellard.c</a>).</p>
|
||||
<h3 id="examples">Examples:</h3>
|
||||
<ul>
|
||||
<li>Sample compilation and execution:</li>
|
||||
|
||||
@@ -39,8 +39,8 @@ of sight: this program is a self-contained speech synthesizer that
|
||||
tells the current time through the computer's sound card - in just under
|
||||
2 Kb of source code !
|
||||
|
||||
In the 2001 IOCCC [rules](../../2001/rules.txt) and
|
||||
[guidelines](../../2001/guidelines.txt) documents, there is no mention of
|
||||
In the 2001 IOCCC [rules](../rules.txt) and
|
||||
[guidelines](../guidelines.txt) documents, there is no mention of
|
||||
what is or isn't acceptable regarding audio I/O, but it is mentioned
|
||||
that hardware-specific and/or non-portable programs are not welcome. So,
|
||||
in order to do audio and satisfy those requirements, the format required
|
||||
|
||||
@@ -172,8 +172,8 @@ to read obviously): when they interact with the user, they only
|
||||
of sight: this program is a self-contained speech synthesizer that
|
||||
tells the current time through the computer’s sound card - in just under
|
||||
2 Kb of source code !</p>
|
||||
<p>In the 2001 IOCCC <a href="../../2001/rules.txt">rules</a> and
|
||||
<a href="../../2001/guidelines.txt">guidelines</a> documents, there is no mention of
|
||||
<p>In the 2001 IOCCC <a href="../rules.txt">rules</a> and
|
||||
<a href="../guidelines.txt">guidelines</a> documents, there is no mention of
|
||||
what is or isn’t acceptable regarding audio I/O, but it is mentioned
|
||||
that hardware-specific and/or non-portable programs are not welcome. So,
|
||||
in order to do audio and satisfy those requirements, the format required
|
||||
|
||||
@@ -83,7 +83,7 @@ terminal!
|
||||
|
||||
#### For the impatient
|
||||
|
||||
The info files `herrmann1.turing` and [herrmann1.gcd](herrmann1.gcd) are sample
|
||||
The info files `herrmann1.turing` and [herrmann1.gcd](%%REPO_URL%%/2001/herrmann1/herrmann1.gcd) are sample
|
||||
programs for the Turing machine. For example, type
|
||||
|
||||
``` <!---sh-->
|
||||
|
||||
@@ -202,7 +202,7 @@ terminal!</p></li>
|
||||
</ul>
|
||||
<h3 id="how-to-use-it">How to use it</h3>
|
||||
<h4 id="for-the-impatient">For the impatient</h4>
|
||||
<p>The info files <code>herrmann1.turing</code> and <a href="herrmann1.gcd">herrmann1.gcd</a> are sample
|
||||
<p>The info files <code>herrmann1.turing</code> and <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/herrmann1/herrmann1.gcd">herrmann1.gcd</a> are sample
|
||||
programs for the Turing machine. For example, type</p>
|
||||
<pre><code> ./herrmann1.sh 'prg=herrmann1.times2'</code></pre>
|
||||
<p>and watch the animated Turing machine multiply 8 by two (in
|
||||
|
||||
@@ -18,8 +18,8 @@
|
||||
./try.sh
|
||||
```
|
||||
|
||||
If you use vi(m) you can see a pattern in [herrmann2.cup](herrmann2.cup) and
|
||||
[herrmann2.ioccc][(herrmann2.ioccc]) by say:
|
||||
If you use vi(m) you can see a pattern in [herrmann2.cup](%%REPO_URL%%/2001/herrmann2herrmann2.cup) and
|
||||
[herrmann2.ioccc][(%%REPO_URL%%/2001/herrmann2herrmann2.ioccc]) by say:
|
||||
|
||||
|
||||
```
|
||||
@@ -32,7 +32,7 @@ and
|
||||
/l
|
||||
```
|
||||
|
||||
For additional fun in [herrmann2.cup](herrmann2.cup) try:
|
||||
For additional fun in [herrmann2.cup](%%REPO_URL%%/2001/herrmann2herrmann2.cup) try:
|
||||
|
||||
|
||||
```
|
||||
@@ -40,7 +40,7 @@ For additional fun in [herrmann2.cup](herrmann2.cup) try:
|
||||
/q
|
||||
```
|
||||
|
||||
and in [herrmann2.ioccc](herrmann2.ioccc) try:
|
||||
and in [herrmann2.ioccc](%%REPO_URL%%/2001/herrmann2herrmann2.ioccc) try:
|
||||
|
||||
```
|
||||
/n
|
||||
|
||||
@@ -158,15 +158,15 @@ Location: <a href="../../location.html#DE">DE</a> - <em>Federal Republic of Germ
|
||||
<pre><code> ./herrmann2</code></pre>
|
||||
<h2 id="try">Try:</h2>
|
||||
<pre><code> ./try.sh</code></pre>
|
||||
<p>If you use vi(m) you can see a pattern in <a href="herrmann2.cup">herrmann2.cup</a> and
|
||||
[herrmann2.ioccc][(herrmann2.ioccc]) by say:</p>
|
||||
<p>If you use vi(m) you can see a pattern in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/herrmann2herrmann2.cup">herrmann2.cup</a> and
|
||||
[herrmann2.ioccc][(https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/herrmann2herrmann2.ioccc]) by say:</p>
|
||||
<pre><code> /[pon]\</code></pre>
|
||||
<p>and</p>
|
||||
<pre><code> /l</code></pre>
|
||||
<p>For additional fun in <a href="herrmann2.cup">herrmann2.cup</a> try:</p>
|
||||
<p>For additional fun in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/herrmann2herrmann2.cup">herrmann2.cup</a> try:</p>
|
||||
<pre><code> /[po]
|
||||
/q</code></pre>
|
||||
<p>and in <a href="herrmann2.ioccc">herrmann2.ioccc</a> try:</p>
|
||||
<p>and in <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/herrmann2herrmann2.ioccc">herrmann2.ioccc</a> try:</p>
|
||||
<pre><code> /n</code></pre>
|
||||
<h2 id="judges-remarks">Judges’ remarks:</h2>
|
||||
<p>Be careful when staring at the source code - your eyes might cross, but
|
||||
|
||||
+1
-1
@@ -163,7 +163,7 @@ the name of the machine running the server, e.g.
|
||||
```
|
||||
|
||||
Make sure that the terminals on both ends are the same size. Also, the TCP port
|
||||
number (by default 5455) specified in the [Makefile](Makefile) mustn't be
|
||||
number (by default 5455) specified in the [Makefile](%%REPO_URL%%/2001/kev/Makefile) mustn't be
|
||||
blocked by a firewall.
|
||||
|
||||
Here's a good quick example to see it in action on your own
|
||||
|
||||
+1
-1
@@ -229,7 +229,7 @@ getting the ball past your opponent’s paddle. It’s pretty fun! :)</p>
|
||||
the name of the machine running the server, e.g.</p>
|
||||
<pre><code> ./kev localhost</code></pre>
|
||||
<p>Make sure that the terminals on both ends are the same size. Also, the TCP port
|
||||
number (by default 5455) specified in the <a href="Makefile">Makefile</a> mustn’t be
|
||||
number (by default 5455) specified in the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/kev/Makefile">Makefile</a> mustn’t be
|
||||
blocked by a firewall.</p>
|
||||
<p>Here’s a good quick example to see it in action on your own
|
||||
machine, assuming you have <code>Xwindows</code>:</p>
|
||||
|
||||
@@ -54,7 +54,7 @@ This is compiled by default; use `westley.sort` as you would `westley` above.
|
||||
|
||||
The author also stated that if you just sort the code you'll get the with
|
||||
`sort`) version that just prints out the punch card. The
|
||||
[westley.punch.c](westley.punch.c) code is specifically so that Westley can punch
|
||||
[westley.punch.c](%%REPO_URL%%/2001/westley/westley.punch.c) code is specifically so that Westley can punch
|
||||
everyone in the face! :-) This is also compiled by default.
|
||||
|
||||
|
||||
@@ -67,7 +67,7 @@ everyone in the face! :-) This is also compiled by default.
|
||||
|
||||
## Alternate code:
|
||||
|
||||
An alternate version of this entry, [westley.alt.c](westley.alt.c), is provided.
|
||||
An alternate version of this entry, [westley.alt.c](%%REPO_URL%%/2001/westley/westley.alt.c), is provided.
|
||||
This alternate code might be less portable.
|
||||
|
||||
|
||||
|
||||
@@ -180,12 +180,12 @@ code by line and it will always sort the order of the input.</p>
|
||||
<h2 id="punch-card-code">Punch card code:</h2>
|
||||
<p>The author also stated that if you just sort the code you’ll get the with
|
||||
<code>sort</code>) version that just prints out the punch card. The
|
||||
<a href="westley.punch.c">westley.punch.c</a> code is specifically so that Westley can punch
|
||||
<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/westley/westley.punch.c">westley.punch.c</a> code is specifically so that Westley can punch
|
||||
everyone in the face! :-) This is also compiled by default.</p>
|
||||
<h3 id="punch-card-try">Punch card try:</h3>
|
||||
<pre><code> echo 'Brian Westley does it again!' | ./westley.punch 2>/dev/null</code></pre>
|
||||
<h2 id="alternate-code">Alternate code:</h2>
|
||||
<p>An alternate version of this entry, <a href="westley.alt.c">westley.alt.c</a>, is provided.
|
||||
<p>An alternate version of this entry, <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2001/westley/westley.alt.c">westley.alt.c</a>, is provided.
|
||||
This alternate code might be less portable.</p>
|
||||
<h3 id="alternate-build">Alternate build:</h3>
|
||||
<pre><code> make alt</code></pre>
|
||||
|
||||
Reference in new issue
Block a user