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.
1.4 KiB
1.4 KiB
To build:
make
To use:
./toledo1 [0-9][0-9]
where [0-9][0-9] is a two digit number.
Try:
./try.sh
Judges' remarks:
For most of the arguments (e.g. those above) the resulting path is not circular, but at least one starting point yields a circular path.
Why do some of the "illegal" starting points work more or less as could be expected, and some dump core?
Author's remarks:
Can you place a knight on a chess board and make it visit the 64 squares without repeating them?
If not, this program does it, just run it with an argument giving initial position.
./toledo1 11 # start is A8
./toledo1 18 # start is H8
./toledo1 81 # start is A1
./toledo1 88 # start is H1
./toledo1 44 # start is D5
It will print move order. The algorithm is so simple that you can read it in the source code. At the first glance it can appear checkered. Nevertheless, don't be dismayed, jar, jar. :-)