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
@@ -129,15 +129,15 @@ Or even simpler:
|
||||
cat august.c test.oc | ./august | ./august
|
||||
```
|
||||
|
||||
A larger example is included [fac.oc](fac.oc).
|
||||
A larger example is included [fac.oc](%%REPO_URL%%/1996/august/fac.oc).
|
||||
|
||||
The compiler for OC is naturally written in OC (where did you think the byte
|
||||
code came from?). It is in the file [parse.oc](parse.oc).
|
||||
code came from?). It is in the file [parse.oc](%%REPO_URL%%/1996/august/parse.oc).
|
||||
|
||||
Hmm... So now we have an interpreter written in OC and a compiler for OC, can
|
||||
we compile the interpreter? Yes, we can! The OC compiler does not have a
|
||||
preprocessor (hey, what do you expect from a program that is this small), so we
|
||||
need to use an external one. To pre-process [august.c](august.c) use the
|
||||
need to use an external one. To pre-process [august.c](%%REPO_URL%%/1996/august/august.c) use the
|
||||
command from the Makefile, but add the `-E` flag and change 60000 to 40000,
|
||||
i.e.:
|
||||
|
||||
|
||||
@@ -213,13 +213,13 @@ and binary in august) and that we have this in a file named <code>test.oc</code>
|
||||
<pre><code> ./august < test.oo</code></pre>
|
||||
<p>Or even simpler:</p>
|
||||
<pre><code> cat august.c test.oc | ./august | ./august</code></pre>
|
||||
<p>A larger example is included <a href="fac.oc">fac.oc</a>.</p>
|
||||
<p>A larger example is included <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/august/fac.oc">fac.oc</a>.</p>
|
||||
<p>The compiler for OC is naturally written in OC (where did you think the byte
|
||||
code came from?). It is in the file <a href="parse.oc">parse.oc</a>.</p>
|
||||
code came from?). It is in the file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/august/parse.oc">parse.oc</a>.</p>
|
||||
<p>Hmm… So now we have an interpreter written in OC and a compiler for OC, can
|
||||
we compile the interpreter? Yes, we can! The OC compiler does not have a
|
||||
preprocessor (hey, what do you expect from a program that is this small), so we
|
||||
need to use an external one. To pre-process <a href="august.c">august.c</a> use the
|
||||
need to use an external one. To pre-process <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/august/august.c">august.c</a> use the
|
||||
command from the Makefile, but add the <code>-E</code> flag and change 60000 to 40000,
|
||||
i.e.:</p>
|
||||
<pre><code> cc -E -DZ=40000 .... august.c > august.oc</code></pre>
|
||||
|
||||
+1
-1
@@ -31,7 +31,7 @@ For a good no-op try:
|
||||
gzip -c < rcm.c | ./rcm
|
||||
```
|
||||
|
||||
NOTE: this is done in the [try.sh](try.sh) script as well, along with some other
|
||||
NOTE: this is done in the [try.sh](%%REPO_URL%%/1996/rcm/try.sh) script as well, along with some other
|
||||
commands including a way to do the above command but with more steps.
|
||||
|
||||
|
||||
|
||||
+1
-1
@@ -163,7 +163,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
|
||||
<h2 id="judges-remarks">Judges’ remarks:</h2>
|
||||
<p>For a good no-op try:</p>
|
||||
<pre><code> gzip -c < rcm.c | ./rcm</code></pre>
|
||||
<p>NOTE: this is done in the <a href="try.sh">try.sh</a> script as well, along with some other
|
||||
<p>NOTE: this is done in the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/rcm/try.sh">try.sh</a> script as well, along with some other
|
||||
commands including a way to do the above command but with more steps.</p>
|
||||
<h2 id="authors-remarks">Author’s remarks:</h2>
|
||||
<p>Except for some silly requirements regarding input validation, CRC checking, and
|
||||
|
||||
@@ -41,14 +41,14 @@ The author also suggests:
|
||||
```
|
||||
|
||||
(and we do too) which works with `sh`, `bash`, `ksh` and `zsh` as well. Press
|
||||
ctrl-c to stop it. Observe how the [try.sh](try.sh) script does this once to
|
||||
ctrl-c to stop it. Observe how the [try.sh](%%REPO_URL%%/1996/schweikh2/try.sh) script does this once to
|
||||
make it easier to see what is happening.
|
||||
|
||||
|
||||
## Judges' remarks:
|
||||
|
||||
The original program, with only slight obfuscations, may be found
|
||||
in [hunni.c](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](hunni.pl), obfuscates it
|
||||
appropriately. Try:
|
||||
|
||||
``` <!---sh-->
|
||||
|
||||
@@ -170,11 +170,11 @@ Location: <a href="../../location.html#DE">DE</a> - <em>Federal Republic of Germ
|
||||
<p>The author also suggests:</p>
|
||||
<pre><code> while :; do grep -v '#' schweikh2.c; done</code></pre>
|
||||
<p>(and we do too) which works with <code>sh</code>, <code>bash</code>, <code>ksh</code> and <code>zsh</code> as well. Press
|
||||
ctrl-c to stop it. Observe how the <a href="try.sh">try.sh</a> script does this once to
|
||||
ctrl-c to stop it. Observe how the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/schweikh2/try.sh">try.sh</a> script does this once to
|
||||
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="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="hunni.pl">hunni.pl</a>, obfuscates it
|
||||
appropriately. Try:</p>
|
||||
<pre><code> less hunni.c
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ You have been warned.
|
||||
The source fails to compile on compilers that recognize the inline
|
||||
keyword by default. For gcc, you may need to use `-ansi`.
|
||||
|
||||
See the file [schweikh3.info](schweikh3.info) for example output from various
|
||||
See the file [schweikh3.info](%%REPO_URL%%/1996/schweikh3/schweikh3.info) for example output from various
|
||||
systems.
|
||||
|
||||
But still it is a useful utility. To use try:
|
||||
|
||||
@@ -163,7 +163,7 @@ You have been warned.</p>
|
||||
<h2 id="judges-remarks">Judges’ remarks:</h2>
|
||||
<p>The source fails to compile on compilers that recognize the inline
|
||||
keyword by default. For gcc, you may need to use <code>-ansi</code>.</p>
|
||||
<p>See the file <a href="schweikh3.info">schweikh3.info</a> for example output from various
|
||||
<p>See the file <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1996/schweikh3/schweikh3.info">schweikh3.info</a> for example output from various
|
||||
systems.</p>
|
||||
<p>But still it is a useful utility. To use try:</p>
|
||||
<pre><code> ./schweikh3</code></pre>
|
||||
|
||||
Reference in new issue
Block a user