In Gambit 17, Gambit's "core" C++ code will comprise the contents of src/core, src/games and src/solvers. Heretofore, these have just been linked directly into the graphical interface and command-line tool executables.
We will also expose the C++ code as a separately-buildable library, which can be called from C++ code (or a wrapper for another language someone might choose to create).
- Revising the autotools build files to do this should be straightforward.
- The API for this will not initially be as stable or documented as
pygambit; documentation should reflect this.
- Relatedly, we will likely be a bit lazy about header files - most of the header files need to be "public" anyway as the code is currently configured so we can make them all installed
- This will be a good opportunity to clean up and standardise the file descriptions, paths, and
#ifdef header guards.
- We have an existing Doxygen config file, which should be reviewed and updated to build minimal documentation, taking advantage of the Doxygen markup where it does exist
In Gambit 17, Gambit's "core" C++ code will comprise the contents of
src/core,src/gamesandsrc/solvers. Heretofore, these have just been linked directly into the graphical interface and command-line tool executables.We will also expose the C++ code as a separately-buildable library, which can be called from C++ code (or a wrapper for another language someone might choose to create).
pygambit; documentation should reflect this.#ifdefheader guards.