Many improvements to 2005/giljade presentation
The try.sh script lets one experience the entry without having to use vi(m) .. you know, in case they're afraid of getting stuck :-) (and it is easier too). The script leaves the file there (rather than piping to less(1)) so that one can view it in a text editor if they wish. The file test.sh runs the test suite mode but it filters out the running of 'make', instead only showing the lines matching '^Line'. When it's all done it checks if 180 versions (lines) were found (it writes to stdout and another file with tee(1)). If it does not find 180 it is an error and this is reported (with exit 1). If it does find 180 all is good. The make test rule was added and uses this script. Format and typo check README.md file.
This commit is contained in:
Cody Boone Ferguson committed
1 parent
ea2f4dbb30
commit
a9fbaf593f
5 files changed
+134
-42
No files matched your search
@@ -119,8 +119,8 @@ OBJ= ${PROG}.o
|
||||
DATA=
|
||||
TARGET= ${PROG}
|
||||
#
|
||||
ALT_OBJ= ${PROG}.alt.o
|
||||
ALT_TARGET= ${PROG}.alt
|
||||
ALT_OBJ=
|
||||
ALT_TARGET=
|
||||
|
||||
|
||||
#################
|
||||
@@ -136,18 +136,16 @@ all: data ${TARGET}
|
||||
sandwich supernova deep_magic magic charon pluto
|
||||
|
||||
${PROG}: ${PROG}.c
|
||||
@echo "NOTE: this version cannot successfully run the self-test. Use make alt"
|
||||
@echo "for a version which will work. See README.md for why it is this way."
|
||||
${CC} ${CFLAGS} $< -o $@ ${LDFLAGS}
|
||||
|
||||
test: ${PROG} test.sh
|
||||
./test.sh
|
||||
|
||||
# alternative executable
|
||||
#
|
||||
alt: data ${ALT_TARGET}
|
||||
@${TRUE}
|
||||
|
||||
${PROG}.alt: ${PROG}.alt.c
|
||||
${CC} ${CFLAGS} $< -o $@ ${LDFLAGS}
|
||||
|
||||
# data files
|
||||
#
|
||||
data: ${DATA}
|
||||
@@ -212,7 +210,7 @@ clean:
|
||||
fi
|
||||
|
||||
clobber: clean
|
||||
${RM} -f ${TARGET} ${ALT_TARGET}
|
||||
${RM} -f ${TARGET} ${ALT_TARGET} out
|
||||
@-if [ -e sandwich ]; then \
|
||||
${RM} -f sandwich; \
|
||||
echo 'ate sandwich'; \
|
||||
|
||||
+18
-24
@@ -4,17 +4,6 @@
|
||||
make
|
||||
```
|
||||
|
||||
NOTE: if you do not have access to a compiler that lets you have alternative arg
|
||||
types to `main()` the self-test feature will fail. If your compiler does not
|
||||
have this defect you can use the Alternate code described below. The reason to
|
||||
have it as the alternate version is that there is more to the entry that can
|
||||
still be enjoyed with compilers with the `main()` args defect including the
|
||||
primary purpose of the entry, a puzzle.
|
||||
|
||||
Hopefully this will be resolved in time where there is no need for an alternate
|
||||
version but it's a complicated one. See also the [bugs.md](/bugs.md) file for
|
||||
more information.
|
||||
|
||||
|
||||
### Bugs and (Mis)features:
|
||||
|
||||
@@ -45,7 +34,7 @@ Open an xterm with 78 lines.
|
||||
vi out
|
||||
```
|
||||
|
||||
Press ^F (control F) repeatedly.
|
||||
Press `^F` (control F) repeatedly.
|
||||
|
||||
|
||||
### Self-test feature to try:
|
||||
@@ -58,9 +47,10 @@ Press ^F (control F) repeatedly.
|
||||
|
||||
## Judges' remarks:
|
||||
|
||||
This entry takes editorial in how it deals with its output. After using
|
||||
vi to look at the source, use vi to look at its output. We especially
|
||||
recommend it on a 78 column xterm while leaning on Control-F.
|
||||
This entry takes editorial in how it deals with its output. After using `vi(1)`
|
||||
(or `vim(1)`) to look at the source, use `vi(1)` (or `vim(1)`) to look at its
|
||||
output. We especially recommend it on a 78 column xterm while leaning on
|
||||
Control-F.
|
||||
|
||||
If you really understand expressions, then understand this:
|
||||
|
||||
@@ -76,9 +66,10 @@ s=s^(b=s&s-1^s)
|
||||
### So what do we have here ?
|
||||
|
||||
Just run the executable with no command line args and look at the output. In
|
||||
order to properly enjoy it you will need two good old programs: xterm and vi.
|
||||
Do the following: open an xterm with precisely 78 lines, and use the tiny font
|
||||
size for best results. Then vi (vim will also do) the output. Type `^F`
|
||||
order to properly enjoy it you will need two good old programs: `xterm(1)` and
|
||||
`vi(1)` (or `vim(1)`).
|
||||
Do the following: open an `xterm(1)` with precisely 78 lines, and use the tiny font
|
||||
size for best results. Then `vi(1)` (`vim(1)` will also do) the output. Type `^F`
|
||||
repeatedly or hold it down and enjoy the show ...
|
||||
|
||||
The program solves (very very fast) a sliding block puzzle. There are many
|
||||
@@ -100,7 +91,7 @@ Actually, This program is smarter than merely printing ITSELF in 180 different
|
||||
layouts. It is self-improving, in that the programs it prints have three
|
||||
advantages over the original:
|
||||
|
||||
1. Their layout is more precise (Notice the annoying \ at the 10'th line of
|
||||
1. Their layout is more precise (Notice the annoying `\` at the 10'th line of
|
||||
the original program which is actually a 'layout bug').
|
||||
|
||||
2. Their binary output does not rely on the source file being in the same
|
||||
@@ -108,7 +99,7 @@ directory, and will not dump core if it doesn't (like the original does). :)
|
||||
|
||||
3. They have much more comments (Not very helpful ones though).
|
||||
|
||||
In addition as we all know bugs can creep on us in the most unexpected of
|
||||
In addition as we all know bugs can creep up on us in the most unexpected of
|
||||
places, and checking that indeed the output is composed of 180 legal C
|
||||
programs by hand can be quite tedious, hence the program also include a self-
|
||||
test mode. Just run it with the output file as command line argument. It will
|
||||
@@ -124,7 +115,8 @@ but this can easily be done. Try it and diff the output of any of the 180
|
||||
results with the original output. Of course all 180 programs also include the
|
||||
self-test mode.
|
||||
|
||||
### Why I think this program is obfuscated.
|
||||
|
||||
### Why I think this program is obfuscated
|
||||
|
||||
* Because it says so, and twice is better than once!
|
||||
* All the usual suspects i.e. `?:`, `&&`, `||`, `,` used to compress code
|
||||
@@ -134,7 +126,7 @@ variable names, etc...
|
||||
the algorithm that is used to generate possible moves is extremely efficient.
|
||||
|
||||
In fact it can compute several moves in parallel on one processor! Moreover
|
||||
Only the most efficient bitwise logical operations, shift,and subtraction by
|
||||
only the most efficient bitwise logical operations, shift,and subtraction by
|
||||
one is used. No inefficient conditional tests and jumps are needed in that
|
||||
part of the program.
|
||||
* The single expression I'm most proud of, and would have submitted to the
|
||||
@@ -154,9 +146,10 @@ interesting.
|
||||
when returning to it now I had to sweat quite a lot to understand the f\*\*\*ing
|
||||
mess I've made.
|
||||
|
||||
|
||||
### Known Bugs/problems/warnings/portability issues
|
||||
|
||||
Some `CPP`s issue a warning about empty macro parameters.
|
||||
Some `cpp`s issue a warning about empty macro parameters.
|
||||
|
||||
`-pedantic` informs me that 'ISO C' does not allow extra ; outside of a
|
||||
function, and to this I say to ISO what ???
|
||||
@@ -166,7 +159,7 @@ and remove some unnecessary expressions, and to this I say: if I listen to you
|
||||
where is my freedom to obfuscate in style?
|
||||
|
||||
As mentioned earlier if you try to run the original program without its source
|
||||
nearby it will dump core.
|
||||
in the working directory it will dump core.
|
||||
|
||||
The program relies heavily on the ASCII coding system (have I seen this
|
||||
comment before ?). It also implicitly assumes that `sizeof(int) = sizeof(FILE
|
||||
@@ -191,6 +184,7 @@ program.
|
||||
Use the program to solve for board size different than `4*5`. That's a bit more
|
||||
tricky.
|
||||
|
||||
|
||||
### Hint for the challenges
|
||||
|
||||
Just try to change the program, and use the self test to see what happens ...
|
||||
|
||||
Executable
+34
@@ -0,0 +1,34 @@
|
||||
#!/usr/bin/env bash
|
||||
#
|
||||
# test.sh - demonstrate IOCCC winner 2005/giljade test suite feature
|
||||
#
|
||||
|
||||
# make sure CC is set so that when we do make CC="$CC" it isn't empty. Doing it
|
||||
# this way allows us to have the user specify a different compiler in an easy
|
||||
# way.
|
||||
if [[ -z "$CC" ]]; then
|
||||
CC="cc"
|
||||
fi
|
||||
|
||||
make CC="$CC" all >/dev/null || exit 1
|
||||
|
||||
GILJADE="giljade"
|
||||
EXIT_CODE=0
|
||||
|
||||
rm -f out out.count
|
||||
|
||||
./"$GILJADE" > out
|
||||
./"$GILJADE" out | tee out.count | grep '^Line'
|
||||
COUNT="$(grep -c '^Line' out.count)"
|
||||
|
||||
if [[ "$COUNT" != 180 ]]; then
|
||||
echo "FAIL: expected 180 versions, got $COUNT" 1>&2
|
||||
EXIT_CODE=1
|
||||
else
|
||||
echo "Found all 180 versions!" 1>&2
|
||||
fi
|
||||
|
||||
rm -f out out.count
|
||||
|
||||
exit "$EXIT_CODE"
|
||||
|
||||
Executable
+34
@@ -0,0 +1,34 @@
|
||||
#!/usr/bin/env bash
|
||||
#
|
||||
# try.sh - demonstrate IOCCC winner 2005/giljade
|
||||
#
|
||||
|
||||
# make sure CC is set so that when we do make CC="$CC" it isn't empty. Doing it
|
||||
# this way allows us to have the user specify a different compiler in an easy
|
||||
# way.
|
||||
if [[ -z "$CC" ]]; then
|
||||
CC="cc"
|
||||
fi
|
||||
|
||||
make CC="$CC" all >/dev/null || exit 1
|
||||
|
||||
# clear screen after compilation so that only the entry is shown
|
||||
clear
|
||||
|
||||
read -r -p "Do you wish to run the test suite (y/n) ? "
|
||||
if [[ "$REPLY" == "y" ]]; then
|
||||
echo "$ make test" 1>&2
|
||||
make test
|
||||
fi
|
||||
|
||||
echo 1>&2
|
||||
echo "$ ./giljade > out" 1>&2
|
||||
./giljade > out
|
||||
echo "For this next step, make sure to keep pressing space (or hold it down) (q = quit)." 1>&2
|
||||
echo "$ less out" 1>&2
|
||||
read -r -n 1 -p "Press any key to continue: "
|
||||
less out
|
||||
|
||||
echo "We've left the file 'out' for you in case you wish to open it in vi(m). If" 1>&2
|
||||
echo "you do we recommend you try holding ctrl-f down in a similar way to how you held" 1>&2
|
||||
echo "down space above. Of course you can open it in another editor if you wish." 1>&2
|
||||
+42
-10
@@ -15,8 +15,9 @@ responsible for most of the improvements and fixes including many **EXTREMELY
|
||||
HARD bug fixes** like
|
||||
[1988/phillipps](/thanks-for-fixes.md#1988phillipps-readmemd),
|
||||
[1992/vern](/thanks-for-fixes.md#1992vern-readmemd),
|
||||
[2001/anonymous](/thanks-for-fixes.md#2001anonymous-readmemd) and
|
||||
[2004/burley](/thanks-for-fixes.md#2004burley-readmemd), making entries like
|
||||
[2001/anonymous](/thanks-for-fixes.md#2001anonymous-readmemd),
|
||||
[2004/burley](/thanks-for-fixes.md#2004burley-readmemd) and
|
||||
[2005/giljade](/thanks-for-fixes.md#2005giljade-readmemd), making entries like
|
||||
[1985/sicherman](/thanks-for-fixes.md#1985sicherman-readmemd) and
|
||||
[1986/wall](/thanks-for-fixes.md#1986wall-readmemd) not need `-traditional-cpp`
|
||||
(all **EXTREMELY HARD**), fixing entries to work with clang (some being
|
||||
@@ -2905,18 +2906,49 @@ as it caused a compilation error in some of the generated code but served no
|
||||
purpose, didn't affect the output of the puzzle and since the 'string' is
|
||||
already in the code there is no problem omitting it.
|
||||
|
||||
`main()` was also changed to be in the old format:
|
||||
The most complicated fix was for, as might be expected, `clang`: it (at least
|
||||
some systems?) has `-Werror` by default so the program was changed to use `make`
|
||||
and then `rm -f` on the output of the compiled binary instead. This change might
|
||||
also not have been necessary if using different flags to `cc` but this is less
|
||||
portable and caused other problems. This was a complicated fix as it's in the
|
||||
comments but in a funny way; the final result to get the test feature to work
|
||||
is:
|
||||
|
||||
```diff
|
||||
-(B[h]=N-B,N= N+6);}main(int Z,char**Y ){char*U=Z ;
|
||||
+(B[h]=N-B,N= N+6);}main(Z,Y )char**Y;{char*U=Z ;
|
||||
```c
|
||||
;; /*echo/Line/%d;sed/-n/-e/ %d,%dp/%s/|sed*/
|
||||
/*-e/'s,intZ,int/ Z,g'>c.c;make/c;/ rm/-f/c*/
|
||||
;;
|
||||
```
|
||||
|
||||
Finally because clang has `-Werror` by default the program was changed to use
|
||||
`make` and then `rm -f` on the output of the compiler instead. This change might
|
||||
also not have been necessary if using different flags to `cc` but this felt
|
||||
cleaner, somehow.
|
||||
changed from:
|
||||
|
||||
```c
|
||||
;; /*echo/Line/%d;sed/-n/-e/ %d,%dp/%s>*/
|
||||
/*c.c;cc/c.c /-c*/;;
|
||||
```
|
||||
|
||||
or as a diff:
|
||||
|
||||
|
||||
```diff
|
||||
-(t(m),(0));; /*echo/Line/%d;sed/-n/-e/ %d,%dp/%s>*/
|
||||
-/*c.c;cc/c.c /-c*/;;char*A=0,*_,*R,*Q, D[9999],*r,l
|
||||
-[9999],T=42, M,V=32;long*E,k[9999],B[1 <<+21],*N=B+
|
||||
+(t(m),(0));; /*echo/Line/%d;sed/-n/-e/ %d,%dp/%s/|sed*/
|
||||
+/*-e/'s,intZ,int/ Z,g'>c.c;make/c;/ rm/-f/c*/
|
||||
+;;char*A=0,*_,*R,*Q, D[9999],*r,l[9999],T=42, M,V=32;int *E,k[9999],B[1 <<+21],*N=B+
|
||||
```
|
||||
|
||||
Cody also added the [try.sh](2005/giljade/try.sh) script which also lets one see
|
||||
the beauty of the entry without having to use vi(m), should they be afraid of
|
||||
getting stuck in it (and for ease of use). :-)
|
||||
|
||||
Finally, to improve upon the test-suite provided by the program, Cody added the
|
||||
`make test` rule which only shows lines matching `'^Line'` but writing to a
|
||||
temporary file the compilation including the 'Line' lines. After that is done it
|
||||
uses `grep -c` on the file to show that there are indeed as many versions the
|
||||
program generates as the author states, 180. If it does not find 180 it is an
|
||||
error; otherwise it is success. It uses [test.sh](2005/giljade/test.sh).
|
||||
|
||||
|
||||
## [2005/jetro](2005/jetro/jetro.c) ([README.md](2005/jetro/README.md))
|
||||
|
||||
Reference in new issue
Block a user