Very next things to do: add tests based on book notation examples, start writing code documentation, parser for user input notation. Normally, I would continue writing parser, since that would bring the most value to the table.
There are already tests which do most of transformations to chessboard, and most of notations, so it's not the most pressing thing to do. However, tests based on book examples would provide value in that it's already in the book how application should behave. Sometimes covering all the features also reveals shortcomings in implementation, and it shouldn't be all that difficult to write all book tests, only tedious.
There are also some 6k+ sloc in C already, and I kinda see things coming up together, so it might be prudent to start documenting library. Things are easily forgotten, especially in a slowly, but surely growing code-base. I have already tested doxygen, worked out-of-box, and I didn't exactly liked it. Might try Sphinx, liked it using it for Python sources, will see.
No comments:
Post a Comment