In your repository the branch feedback in the file Feedback.md is a Claude (LLM) analysis of the team history for Exercise 33: Team Text Match. I suggest viewing it at GitHub.
Read over the analysis and think about what can be improved, not only about your current version of the code, but also about your process. Even if your process worked and you did well, consider how you can parallelize your development (instead of waiting while someone else makes changes).
Follow the instructions for Exercise 33: Team Text Match
The targets from last time were: make clean
, make run
, make test
Once you have all those targets implemented, implement the following:
Add the target manpage
, i.e., make manpage
, that creates a man page. This was added to the build-files-020. Note that my example also added a comment.
The manpage will be named textmatch.1
. It is generated from the markdown file textmatch.1.md
. This conversion uses the command lowdown
. It is not installed in your GitHub Codespace. However, you do have the permissions to install it. First, update
Then install the package:
If you are in WSL, you need to use sudo
before each command. On macOS, brew install lowdown
man
, i.e., make man
, that views the created manpage. This was also added to the build-files-010, and it has its own comment.textmatch
executable and its object files.regexCountTest.cpp
executable and its object files.clean
targetrun
targetAs before, this is due by the end of class. No commits outside of class.