Changelog

All notable changes to Dangl.Calculator are documented here.

v2.2.0:

Dropped tests for net6.0 and addes tests for net8.0
Added a new overload to the calculator which accepts an options object. Additionally, it is now possible to configure a special case that applies different handling for formulas that start with a negative power, e.g. -2^2. This would typically be parsed as (-2)^2, but with the new option, it can be configured to be parsed as -(2^2). It is not recommended to use this option, since most other software (e.g. Microsoft Excel and Google Sheets) do also not behave in that way.
Square [] and curly {} parentheses are now also valid for formulas. They are only used to group expressions, and implicit multiplication like 2(3)=6 is not allowed with those

The ANTLR dependencies were updated from Antlr.Runtime to Antlr.Runtime.Standard. The new package is the now official ANTLR runtime package and includes many performance improvements
Compatibility for net40 and netstandard1.1 was dropped, the lowest supported frameworks now are ´net45andnetstandard2.0`
Dropped tests for net5.0 and added tests for net7.0

The calculator now supports trailing comments in a formula, separated by a semicolon ; at the end of the actual formula input. For example, 1 + 2; Hello World! now just evaluates 1 + 2 and ignores everything after the semicolon ;

The generated assemblies now have a strong name. This is a breaking change of the binary API and will require recompilation on all systems that consume this package. The strong name of the generated assembly allows compatibility with other, signed tools. Please note that this does not increase security or provide tamper-proof binaries, as the key is available in the source code per Microsoft guidelines

CI tests are now also run on Linux
Added capability to detect missing multiplication signs, e.g. the formula 3pi is now recognized as 3*pi or 2(3) as 2*(3)

Bugfix: Fixed operator precedence for exponential expression, e.g. 1e+2*2 == 200

Bugfix: Unary minus signs were not always evaluated to the nearest matching expression, e.g. -3+5 was evaluated as -(3+5). See GitHub Issue #1