convince mpsolve authors to provide the version number to the program

[DanGrayson]

... so we can fix this line in d/version.dd:

   "mpsolve version" => "3.1.8", -- TODO: DETERMINE VERSION #??

, which hardcodes the version as 3.1.8.

[DanGrayson]

I've written to the authors requesting the feature.

[d-torrance]

If the command-line tool is available during build, then we could get it that way:

profzoom@gloria:~/tmp/mpsolve/usr/bin$ ./mpsolve -v | sed 's/MPSolve //'
3.1.8

[DanGrayson]

It is, and we're even distributing it, but it will probably be simpler just to wait for the feature.

[robol]

We can definitely add that; I opened an issue on MPSolve's repo to track it, I will probably implement it soon.

Also, a slightly unrelated notice: I expect that we may release 3.1.9 with some bugfixes (and likely this change), and later there will be a major version bump because we are in the process of renaming our multiprecision floating point complex type to avoid a name clash with GNU MPC. This will break the API, although anyone not accessing directly multiprecision complex roots won't be affected.

[DanGrayson]

Thanks!

[robol]

I added new functions mps_get_major_version(), mps_get_minor_version(), mps_get_patch_version() are available in the latest release (3.2.1), along with a string representation with mps_get_version().

There are also defines statements included in the main header as follows (for 3.2.1)

#define MPS_MAJOR_VERSION 3
#define MPS_MINOR_VERSION 2
#define MPS_PATCH_VERSION 1

Best, -- Leonardo.

[DanGrayson]

Thank you!