Landon Curt Noll
4ee4c731f7
While not strictly necessary, replacing the two ASCII tab characters in the markdown copyright comment makes it easier to detect problematic TAB indentation within markdown files. After this commit, only 90 markdown files have leading ASCII TAB characters. And again, while not strictly necessary, we can consider running expand on those 90 markdown files to see what effect that might have on the HTML files they produce. Replace leading ASCII TAB characters with multiples of 8 ASCII SPACE characters (the default action of the `expand(1)` tool) might have an negative effect on some HTML formatting where **hack-a-round** formatting was attempted to fix broken indentation caused by problematic ASCII TAB characters. Think of this as a baseline for evaluating leading TAB characters within markdown files. TODO: Consider either using `expand(1)` to replace leading ASCII TAB characters with multiples of 8 ASCII SPACE characters AND/OR modifying the appropriate `bin` tool to convert leading ASCII TAB characters into multiples of 8 ASCII SPACE characters.
83 lines
2.6 KiB
Markdown
83 lines
2.6 KiB
Markdown
## To build:
|
|
|
|
``` <!---sh-->
|
|
make all
|
|
```
|
|
|
|
|
|
## To use:
|
|
|
|
``` <!---sh-->
|
|
./bas1.sh
|
|
```
|
|
|
|
|
|
## Judges' remarks:
|
|
|
|
The output is supposed to be a 3D maze, but it is somewhat more
|
|
than that. If you've seen any of the [Maurits
|
|
Escher's](https://en.wikipedia.org/wiki/M._C._Escher)
|
|
[works](https://mcescher.com/gallery/), you'll know what we're talking about.
|
|
|
|
When trying to run the program with command line arguments, be generous.
|
|
|
|
|
|
## Author's remarks:
|
|
|
|
### BEMAZING
|
|
|
|
"You're in a twisty little maze of beams, all different."
|
|
|
|
`Bemazing` is "amazing" taken one step (letter) further. `Bemazing`
|
|
creates a 3D maze of beams. Try to go from the entrance (the
|
|
unfinished beam in one corner) to the exit (the unfinished beam in the
|
|
opposite corner) or vice versa.
|
|
|
|
For maximum portability, `Bemazing` is not tied to any window system, but
|
|
creates postscript output. The picture it makes will fit on either A4 or letter
|
|
size paper.
|
|
|
|
In addition, because postscript is rather verbose, `Bemazing` creates
|
|
the postscript in `gzip(1)` format, in order to save precious bits on your
|
|
hard disk for the latest version of [GNU
|
|
Emacs](https://www.gnu.org/software/emacs/) (after all, you wouldn't
|
|
want to use an editor without a psychoanalyze-pinhead function, now
|
|
would you). Again for maximum portability, `Bemazing` will take special
|
|
care that the binary output will not contain any newline or return
|
|
characters that may get weird treatment on systems that do not use the
|
|
One True Line Separator.
|
|
|
|
|
|
### NOTES
|
|
|
|
Be sure to view the source with something that can display characters
|
|
`\240-\377`. Use `LESSCHARSET=latin1`, `M-x` `standard-display-european` in
|
|
GNU Emacs etc. The source does not use characters in the range
|
|
`\200-\237` (we are not an unnamed word processor that tends to create
|
|
HTML containing these control characters).
|
|
|
|
Because this is not the obfuscated postscript contest, the postscript
|
|
does not contain any `for`, `if` or other control structures. All the
|
|
logic is in the C code. There are only a few straightforward `def`s,
|
|
because otherwise the output would become much larger.
|
|
|
|
Try running `Bemazing` with command line arguments and see what
|
|
happens. (But note that the program only guarantees that there
|
|
actually is a route from entrance to exit if you run it without
|
|
command line arguments.)
|
|
|
|
|
|
<!--
|
|
|
|
Copyright © 1984-2024 by Landon Curt Noll. All Rights Reserved.
|
|
|
|
You are free to share and adapt this file under the terms of this license:
|
|
|
|
Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)
|
|
|
|
For more information, see:
|
|
|
|
https://creativecommons.org/licenses/by-sa/4.0/
|
|
|
|
-->
|