Hey Informach,
Thanks for the answer. I'm looking forward to the next firmware update. Also, I noticed that there is a problem using the solver apps and the CAS solve functions when you setup the calculator to 1.000.000,1 instead of 1,000,000.1. It doesn't recognise the extra dots in the number and starts changing the numbers.
Okay, Tim
I didn't know that, thanks!
(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. :-(
Thanks for your explanation, Tim. It gets difficult to explain when my results differ from those of others at times like these. Usually, I don't even try, as I don't know, and it just deteriorates from that point! Also, thanks for all of your diligent work and the special help offered us, here. From my point of view, I see the prime as still somewhat evolving, much better now, but perhaps still room to summit the mountain. Having guidance from your side, is well appreciated.
-Dale-
Hi Tim,
Thank you very, very much for your explanation!