Bug in solve app?

[Tim Wessman]

(05-10-2016 07:12 AM)Dirk.nl Wrote:  Okay, Tim

I didn't know that, thanks!

For example, I get this as the output for A,B,C,D on the last example now.

2.50125062531e−3,−3.75187593797e−2,−0.562781390695,8.4392196098

Which works out to within the numerical precision of the system.

The root cause of the issue happened between the last public release (8151) and the ios release. Internally, the string routines used wchar_t as the character type. However, wchar_t is not portable between systems and is 32 bits on linux/osx, but 16bits on ARM/windows. We had to work on all the files, strings, and data storage for the whole system to ensure file compatibility between systems (also to be 32/64 bit compatible). Unfortunately, we did miss this case in the solver. :-(