3 - some positions show problem in the evaluation algorithm
4 - minishogi repetition rule, different from standard shogi, is
6 - with no piece on board, computer generates invalid move
10 - use ~/.gnushogi for binary book and hash file
12 - make minishogi a run-time option rather than a compile-time one,
13 using the "variant" mechanism of the xboard protocol
17 - switch cli parsing to getopt
18 - hunt for extern's and prototypes spread all over the source
19 - hunt for more hardcoded variant-specific constants
20 - position of captured pieces in curses mode
21 - compile with bound-checker
22 - add autosave mode to ease hunt for segfaults ?
23 - ? use 2D array for the board, get rid of the (i)nunmap stuff
24 - fixup build procedure to support parallel make runs
25 - investigate those preexisting "overflow in implicit constant
28 Minishogi-related stuff
31 - tune difficulty levels
32 - other tunings to investigate
33 * eval.c has lots of heuristic code specific to standard shogi that
34 probably should not been used
35 * PromotionZoneDistanceBonus
37 - add minishogi stuff to the doc
38 - use valid minishogi moves in online help
42 - find out why the engine is so weak
43 - make it battle against Mutz-era gnushogi, and other engines, and
44 compare their evaluation results
45 - see what needs updating in book
46 - express available commands as display-dependant, instead of using if(XSHOGI)
47 - make "help" list commands available for current display
48 - make X and raw two different display drivers