Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Script to redeploy testlib.sml to all exercises on changes. (#206)
* Script to redeploy testlib.sml to all exercises on changes. The directory name `sml-bin` makes the most sense to me for these sml "scripts". Adding them to the makefile also makes it even easier to use these than it is when using "#! /usr/bin/env -S poly --script" as a shebang line. Consequently this should be portable to any Windows system that has GNU make installed, so it is probably better than the shebang. In the code I used the path library to help make things OS portable, but I haven't ever used SML on Windows, so it is untested for that enironment. * Change file perms to 664 for sml-bin/redeploy-testlib.sml I had set it to 775 when it had a shebang and lived in `bin`. Trying to execute it will fail, so it shouldn't be executable. * Make redeploy-testlib phone as well. * Use qualified names. I shouldn't have combined to actions but I did. I removed all unnecessary semicolons while refactoring to use qualified names. Sorry. * Format redeploy-testlib.sml like teslib.sml I also found and removed two more unnecessary semicolons. * Include testlib sync policy in the README. I wrote a brief note about keeping testlib.sml in sync for all exercises in the track, and I mentioned 'make redeploy-testlib' as the provided tool for handling this requirement. I did not elaborate on a policy, because we still don't really have one. Further work related to #110 should result in a clear policy, and at that point the README.md might need some more updating. * Formatting, names, parentheses. * Update README.md Co-authored-by: Victor Goff <keeperotphones@gmail.com> * Add spaces inside tuples. * Use scripts directory instead of sml-bin. * Add a documenting comment to redeploy-testlib.sml. Initially, I thought it must be clear enough from the title/name of the script itself, but on further reflection, a documenting comment might help a non-native english speaker avoid the difficulties of ambiguity. Co-authored-by: Victor Goff <keeperotphones@gmail.com>
- Loading branch information