tinyexpr
tinyexpr copied to clipboard
tiny recursive descent expression parser, compiler, and evaluation engine for math expressions
- Replaces unsafe usages of const void* with appropriate pointer types for data and functions, making the code maximum portable, safe, and easier to maintain. Detail: Some compilers does not...
When I evaluate `(-1)^0` I get -1, which is wrong. Yet when I evaluate `pow(-1, 0)` I get 1, which is correct. It seems to be an expression compilation error...
Newer gcc gets confused when malloc stores a bunch of memory in a one-element array. C99 "flexible array" notation achieves the same effect in a more standard way.
When I build tinyexpr with gcc-11 I get warnings about array subscripts exceeding bounds: ``` % gcc --version gcc (Ubuntu 11.2.0-7ubuntu2) 11.2.0 ``` ``` gcc -Wall -Wshadow -O2 -o smoke...
I think that this warning arises because some CPU architectures have different memory bus sizes for code memory and data memory. Your code uses a single pointer to point to...
I used visual studio 2015 to compile tinyexpr, but I got two compile errors(initializer is not a constant) when meet {"ceil", ceil, TE_FUNCTION1 | TE_FLAG_PURE, 0} and {"floor", floor, TE_FUNCTION1...
i'd love to have math operations that operate with big integers.
### Issue description I've recently discovered via fuzzing with libFuzzer that nested usage of the `ncr()` expression can result in unexpectedly long expression evaluation times. The smallest representation of the...
Added nan check for ncr and fac functions. Now both will return nan, when given nan as parameter. This should resolve #62 Also added .gitignore with the artifacts from make