Inconsistencies and too little info in error messages from math parser
The math parser is often very little informative and inconsistent about errors in expressions. For example, using an undefined variable like this
set: 2*x;
gives "(unexpected token) at line 1", whereas
set: x*2;
correctly gives "(unable to find variable "default::x") at line 1".
A thorough revision would be advisable.