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. Kind regards, Panos -- On Tue, 10 Sep 2019 at 22:59, Sannyasin Brahmanathaswami via use-livecode < use-livecode@lists.runrev.com> wrote: > setPref "preferences/global/lastRunDate", (the seconds) # e.g 1568144731 > > put getPref ("preferences/global/lastRunDate") into tLastRunDate > > returns > {"preferences": > {"global": > {"lastRunDate": 1.56814e+09}, > [snip] > > # we are using jsonImport > > put jsonImport(tJSON) into tPreferencesA > > # handle data and > > put jsonExport(tPreferencesA) into tJSON. > > # thereafter my simple arithmetic functions like > > put (tLastRunDate + 3600) into 1HourLater > > # now throw a "left operand" error.... > > How can we prevent the coercion of simple integer notation to scientific? > > Why is it needed for simple 10 digit number is beyond me. > > There is nothing about automatic coercion in the dictionary. > > BR > > > > > > > > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
