Engine based Json encoding

[Tom Glod]

Hi David,

I would recommend when bringing JSON in from outside, use both, one as the
fallback for the other. JSONTOArray, or JSONImport.
We just implemented this after realising that its just what happens,
sometimes for whatever reason JSON comes back and its not correctly
recognized by either library.
But I've not seen both of them fail on the same piece of JSON.  If you do,
let us know.



On Tue, Jul 14, 2026, 11:44 a.m. David Bovill via use-livecode <
use-livecode at lists.runrev.com> wrote:

> I'm taking a look at the new json handline in Livecode - as it's core to
> what we're working on. I'm getting my head around the new version of Create
> and Classic - so does anyone know any nuances regarding how to tell if it's
> using the native engine version - and any gotcha's regarding encoding -
> I've so many different versions of json handling from the past to ensure
> compatibility:
>
>    - https://future.livecode.com/dp2-json/
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>