Re: Stop Integer Coercion to Scientific Notation in JSON

2019-09-13 Thread Trevor DeVore via use-livecode
On Thu, Sep 12, 2019 at 1:42 PM Sannyasin Brahmanathaswami via use-livecode wrote: > Been working Panos off list. > > There is a caveat, jsonImport and jsonExport not only "display" but > "preserve" the scientific notation as a literal string and math will fail. > > Panos says: must use, (and

Re: Stop Integer Coercion to Scientific Notation in JSON

2019-09-11 Thread panagiotis merakos via use-livecode
Hello all, There is not a lost of precision in the operations. The problem is just that LCB *displays* the value of large numbers in scientific notation, but if you actually do any calculations with the variables that hold these numbers, the calculations are accurate. In other words the

Re: Stop Integer Coercion to Scientific Notation in JSON

2019-09-11 Thread Sannyasin Brahmanathaswami via use-livecode
One tries his best to not get excited by bugs that are left untouched, With some OS's to. keep current, engineering has a tough time, we all know that … but this one pushes a button… bug https://quality.livecode.com/show_bug.cgi?id=18159 How can such a bug go unfixed for three years?

Re: Stop Integer Coercion to Scientific Notation in JSON

2019-09-11 Thread panagiotis merakos via use-livecode
Hello Brahmanathaswami, I think this is because of how currently some handlers in lcb work. See bug https://quality.livecode.com/show_bug.cgi?id=18159 (and the related bugs) for more details. This affects other areas, such as how large numbers are shown in the variables pane in the debugger.

Stop Integer Coercion to Scientific Notation in JSON

2019-09-10 Thread Sannyasin Brahmanathaswami via use-livecode
setPref "preferences/global/lastRunDate", (the seconds) # e.g 1568144731 put getPref ("preferences/global/lastRunDate") into tLastRunDate returns {"preferences": {"global":