Why aren't muparser exceptions inherited from std::exception?

[beltoforion]

Why aren't muparser exceptions inherited from std::exception?

[beltoforion]

std::exception::what is returning a const char* for the error messages. That is unusable for an application which aims for support of wide strings.

[TheQuantumPhysicist]

Whether this is unstable, is debatable, but anyway, you can provide the option for both! You can keep the current options as is, and still inherit from std::exception and override std::exception::what(). Would you consider that?

[beltoforion]

I said unusable not unstable. Sorry but I have no intention of supporting what() and std::exception because i consider it an undesireable workaround. By supporting what() the parser implies the ability to provide a proper error message. For unicode builds i cannot do that. In the end your proposal would create a class which violates the Liskov substitution principle. One might argue that this wouldn't be much of a deal but people will end up bothering me with questions why its not working as they expect and no one will read the documentation.