Jacob Williams
Jacob Williams
Experiment with refactoring the parser to be non-recursive, to see if that speeds up parsing. See #363.
The default path mode uses 1-based arrays (Fortran style), while the RFC6901 mode uses 0-based arrays (C style). Consider adding an option to specify which one to use.
The tests for the latest version (0.10.0) are failing on the [conda-forge feedstock](https://github.com/conda-forge/pdoc3-feedstock). See [here](https://github.com/conda-forge/pdoc3-feedstock/pull/11). One of the errors i see is [ModuleNotFoundError: No module named 'parser'](https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=480438&view=logs&jobId=656edd35-690f-5c53-9ba3-09c10d0bea97&j=656edd35-690f-5c53-9ba3-09c10d0bea97&t=e5c8ab1d-8ff9-5cae-b332-e15ae582ed2d). I think that...
A C/Fortran interface to this would be great. I think it could be added in a similar way that Ipopt has done it.
It might be nice to add support for multiple interpreters (using `Py_NewInterpreter()`, `Py_EndInterpreter()`, etc.)
Consider including [DEFC](http://www.netlib.org/slatec/src/defc.f) a least-squares B-Spline fit from SLATEC.
Currently, we only have 1D integration. For completeness we should have 1D-6D. Note: this project may be useful: https://github.com/jacobwilliams/quadrature-fortran See also #33
Update the CMake config file to enable more control of the build.