Matthew Hambley
Matthew Hambley
It would be handy to have a call or a package variable or something which held the version string for the instance of fparser in use. This would allow depending...
I discovered this problem on code like this: ```fortran use some_mod, only: & #ifdef SPECIAL_CASE first_mod, & second_mod, & #endif third_mod, & fourth_mod ``` So firstly I would like to...
Fortran preprocessors will, by default, often include "line markers" in the processed source. These are used by compilers to give the correct line numbers in the unprocessed source when reporting...
Further to #12, an example of a combined parametrised MPI test would be very useful.
There is a simple example of parametrised which states that it is a complicated topic and to refer to the specific example. Except there is no specific example. Could time...
This new theme offers a number of advantages over our old read-the-docs theme. * Better accessibility * Deeper support for headers * Potentially easier support for versioned documentation
It is well known that using the initialiser syntax on local variables makes them "saved" and therefore global scope, i.e. persistent between calls. This is very rarely useful behaviour in...
Currently configuration must be specified as an argument to the CLI. This is considered to be "per project" configuration. We might also like to support "personal" configuration which is specified...
Developers can be overkeen on global scope variables even when they're not using them to pass arguments to procedures. An outright ban is unworkable as there can be valid reasons...
Each releases documentation is stand alone, which is what we want, but there is no easy way to switch between versions.