beltoforion/muparser

Precedence is different in code vs docs

joemalle opened this issue · 2 comments

joemalle commented

In the code, it seems like and has a higher priority than or: https://github.com/beltoforion/muparser/blob/master/include/muParserDef.h#L208

But in the docs, it seems to be the other way around: https://beltoforion.de/en/muparser/features.php#idDef2

Would be great to fix the docs

beltoforion commented

I will fix the documentation.

beltoforion commented

documentation fixed