forked from Alepha/Alepha
It's mostly worked out, but there's a few odd corner cases, especially around the auto-gen of negation options. It also got me to start thinking about "is a required negatable option still required of its negation?" Similar questions revolve around requiring such options. I'm punting on these for now, but I think it makes sense to perhaps make those incompatible with such domains. Or to treat the two options as a shared-fate unit. But is `-O -o -O -o` a violation of exclusivity? If we wind up returning to the default state, have we actually passed that option, with respect to "requirement"? I have to think about that some more. A commit message isn't the best place to capture this, but I didn't want to lose this thought.
To generate a doxygen reference for Alepha, run "doxygen doxyfile.alepha" A subfolder, DoxygenAlepha, will be created Point a browser to the html/index.html within DoxyAlepha to bring up the main page. The .gitignore file here excludes the DoxyAlepha subfolder in its entirety. If there are too many namespaces in the Class List, consider using Class Index instead. Note: Upgraded to version 1.10.0 to, hopefully get better c++20, including concepts Todo: - create a script to execute doxygen - as part of that script preprocess source file (c++ and header) to remove or simplify namespaces - set the project brief and project logo in doxygen config - customize header and footer
Languages
C++
98.9%
CMake
0.9%
Makefile
0.2%