Format and typo fixes in 1990/stig/README.md

This commit is contained in:
Cody Boone Ferguson committed 2023-04-09 05:36:48 -07:00
1 parent a9d9250afb
commit 88257dc777
1 file changed
+30 -30
+30 -30
View File
@@ -1,55 +1,55 @@
# Strangest Abuse of the Rules
Stig Hemmer
Norwegian Institute of Technology
N-7034 Trondheim-NTH
Norway
Stig Hemmer
Norwegian Institute of Technology
N-7034 Trondheim-NTH
Norway
## To build:
make all
```sh
make all
```
## To run
## To run:
make all
```sh
make all
```
NOTE: that's not a typo or mistake but one can also do:
./o
```sh
./o
```
## Judges' comments
We changed the alias that the author's suggested alias from a
C-shell alias to a zsh alias.
Note that shst.c is renamed to stig.c in the distribution.
Note that `shst.c` is renamed to [stig.c](stig.c) in the distribution.
WARNING: This program's 'how to compile' is too specific to a particular
shell. The obfuscation of this program to more related to
shell obfuscation than C obfuscation. This type of entry will
not be permitted in future contests.
WARNING: This program's `how to compile` is too specific to a particular shell.
The obfuscation of this program is more related to shell obfuscation than C
obfuscation. This type of entry will not be permitted in future contests.
## Author's comments
## Author's comments:
If you like shell programming you may also admire my
creative quoting. (I use echo to create an alias
which when run calls cc with the -D option to create a
C macro with double quotes in it. ARRRRRGGGHHH!)
If you like shell programming you may also admire my creative quoting. (I use
echo to create an alias which when run calls cc with the -D option to create a C
macro with double quotes in it. ARRRRRGGGHHH!)
The program is totally portable, but the compile
commands are very shell specific so don't be TOO mad
at me if they don't work for you.
The program is totally portable, but the compile commands are very shell
specific so don't be TOO mad at me if they don't work for you.
If you want to put these commands in a Makefile you
must add 4 - four - backslashes at the end on first
line. (At least that's what works here.)
If you want to put these commands in a Makefile you must add 4 - four -
backslashes at the end on first line. (At least that's what works here.)
If everything works correctly it create an executable
named c which checks whether your compiler supports
nested comments. I've stolen the `"/*/*/0*/**/1"` from
somewhere so don't give me any points for it. Of
course neither ANSI nor K&R support nested comments
when properly implemented, but what the heck.
If everything works correctly it create an executable named `o` which checks
whether your compiler supports nested comments. I've stolen the `"/*/*/0*/**/1"`
from somewhere so don't give me any points for it. Of course neither ANSI nor
K&R support nested comments when properly implemented, but what the heck.
## Copyright and CC BY-SA 4.0 License: