I'm still watching this for a while now.
As muparser is an external library, I didn't touch this so far. I'd prefer to have this solved in muparser and then update the muparser source in our lib path to stay synced.
There is already an
issue opened in the main
muparser repo on github. I consider to make a pull request there.
To make a pull request, you need a github account.
Fork the project you want to contribute to.
Commit changes to a new branch in your fork repo and sync it with github.
Then it's easy to open a new pull request on the upstream repo.
This is explained in detail on
github help pages.
If you don't have an account now, consider to register one, contributing is much easier then.
Thanks anyway for your efforts.
Armin
investing less than half an hour into Search function can save hours or days of waiting for a solution