mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix Makefile and README.md for 2001/jason

Browse Source
This commit is contained in:
Landon Curt Noll committed 2023-03-18 11:01:35 -07:00
1 parent 83ff856bc9
commit 80bd54903c
2 files changed
+351 -249
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

2001/jason/README.md
+88 -80
View File
@@ -1,4 +1,4 @@
Best Of Show:
# Best Of Show:
Jason Orendorff
5 Buchanan St.
@@ -7,109 +7,117 @@ Best Of Show:
http://www.jorendorff.com/
# To build:
Judge's Remarks:
```sh
make
```
To build:
### To run:
make jason
```sh
./jason
```
Try:
### Try:
./jason
```sh
echo "Do or do not. There is no try."
```
You are in a maze of twisty little passages, all alike.
## Judges' comments:
The really amazing part of this is tha it's a text adventure, and there's
not a single word in the source that isn't a C keyword or function name,
being used as such.
You are in a maze of twisty little passages, all alike.
The interface isn't very tolerant of errors, but you can't really
expect that from something this small.
The really amazing part of this is tha it's a text adventure, and there's
not a single word in the source that isn't a C keyword or function name,
being used as such.
Of particular interest: Go ahead, run it through the preprocessor. You
*still* won't see the words that are used in the game.
The interface isn't very tolerant of errors, but you can't really
expect that from something this small.
Of particular interest: Go ahead, run it through the preprocessor. You
*still* won't see the words that are used in the game.
## Author's comments:
TED shroyer came up with the idea that made it possible to hide all
the text. Thanks, TED. You won. :)
Selected Author's Comments:
$ cc -o prog prog.c
$ ./prog
you are in a maze of twisty little passages
caves lead: left forward back
you see
a lamp
> _
TED shroyer came up with the idea that made it possible to hide all
the text. Thanks, TED. You won. :)
This program is a rather nostalgic little labyrinth game. Start
out by typing "get lamp", then use the direction words "left",
"right", "forward", and "back" to explore the caves. Note that
these words can refer to different passages depending on which way
you're facing. "back" always takes you back the way you came.
Type "quit" to quit.
The maze is randomly generated each time you play. The algorithm
ensures that you start at least 6 hops away from the exit. All
passages are two-way.
$ cc -o prog prog.c
$ ./prog
you are in a maze of twisty little passages
caves lead: left forward back
you see
a lamp
> _
(There is a trick, well-known among adventure game fans, to
keeping one's bearings in games like this. Unless you know the
trick, it can be very difficult to find your way around. Try it
out first; I'll give away the secret at the bottom of this
document.)
This program is a rather nostalgic little labyrinth game. Start
out by typing "get lamp", then use the direction words "left",
"right", "forward", and "back" to explore the caves. Note that
these words can refer to different passages depending on which way
you're facing. "back" always takes you back the way you came.
Type "quit" to quit.
The goal is to collect 8 treasures (plus the lamp) and escape into
the sunlight - or moonlight, as the case may be. After a few
minutes, the lamp runs out of oil, and things become perilous.
The maze is randomly generated each time you play. The algorithm
ensures that you start at least 6 hops away from the exit. All
passages are two-way.
If you manage to escape, you score 50 points for your hide, 50
points per item, and bonus points for speed.
(There is a trick, well-known among adventure game fans, to
keeping one's bearings in games like this. Unless you know the
trick, it can be very difficult to find your way around. Try it
out first; I'll give away the secret at the bottom of this
document.)
Why I think this program is obfuscated:
The goal is to collect 8 treasures (plus the lamp) and escape into
the sunlight - or moonlight, as the case may be. After a few
minutes, the lamp runs out of oil, and things become perilous.
* 70% more # symbols than the average entry.
If you manage to escape, you score 50 points for your hide, 50
points per item, and bonus points for speed.
* Where are all the messages? The game is downright chatty for
only having two string literals ("%d \n" and "Y\n : ! ,.?>").
Why I think this program is obfuscated:
* There is exactly one loop in the program, a for loop, and it is
clearly the product of a deranged mind. Running the
preprocessor only makes it worse.
* 70% more # symbols than the average entry.
* Microsoft Visual C++ won't even compile this program, even
though it is plain ANSI C (*innocent look*) and limits itself to
the most standard and portable of the standard library
facilities.
* Where are all the messages? The game is downright chatty for
only having two string literals ("%d \n" and "Y\n : ! ,.?>").
* Most of the whitespace is significant, so attempts to
beautify it can easily lead to segmentation faults.
* There is exactly one loop in the program, a for loop, and it is
clearly the product of a deranged mind. Running the
preprocessor only makes it worse.
* Attempts to replace the one-character identifiers with longer,
more meaningful names will likewise cause problems. In fact,
simply changing all the Y's to Z's and vice versa results in
some unexpected side effects.
* Microsoft Visual C++ won't even compile this program, even
though it is plain ANSI C (*innocent look*) and limits itself to
the most standard and portable of the standard library
facilities.
When all warnings are enabled, some compilers express the desire
to see a few more parentheses. I respectfully submit that there are
plenty of parentheses in the program (370 in all.) Besides, any
more would put me over the size limit. gcc also generates a
warning about some calculations not being used. Having just spent
19 hours staring at this program, sweating over every character, I
swear gcc is wrong.
* Most of the whitespace is significant, so attempts to
beautify it can easily lead to segmentation faults.
The program is formatted as a poem, to make it more readable.
I find the plaintive chorus "B? B?" particularly poignant.
Also, smiley faces are formatted flush left. (If you don't find
the game entertaining, see if you can find
* Attempts to replace the one-character identifiers with longer,
more meaningful names will likewise cause problems. In fact,
simply changing all the Y's to Z's and vice versa results in
some unexpected side effects.
the fish scales Q)++j<
the shooting star -~- ~ -~i +
When all warnings are enabled, some compilers express the desire
to see a few more parentheses. I respectfully submit that there are
plenty of parentheses in the program (370 in all.) Besides, any
more would put me over the size limit. gcc also generates a
warning about some calculations not being used. Having just spent
19 hours staring at this program, sweating over every character, I
swear gcc is wrong.
The program is formatted as a poem, to make it more readable.
I find the plaintive chorus "B? B?" particularly poignant.
Also, smiley faces are formatted flush left. (If you don't find
the game entertaining, see if you can find
the fish scales Q)++j<
the shooting star -~- ~ -~i +
in the source code.)
in the source code.)
@@ -117,6 +125,6 @@ Selected Author's Comments:
[GAME STRATEGY SPOILER: The trick, of course, is to drop items in
empty rooms to mark them. That way you usually know if you're in a
room you've seen before. It greatly aids mapping.]
[GAME STRATEGY SPOILER: The trick, of course, is to drop items in
empty rooms to mark them. That way you usually know if you're in a
room you've seen before. It greatly aids mapping.]