Hey Kirk, thanks for the post. I'm absolutely _not_ coming to JSON with a 4D perspective. Quite the opposite. JSON is great for many, many things. I'm just used to have tons of options for parsing it and converting it. You get that in <insert name of basically any language>, usually with multiple options. It's just weird that 4D doesn't have a normal JSON suite.
To be clear, I don't think much is missing in this respect over on the C_OBJECT side of the barn, it's the JSON suite that's incomplete. JSON should always be manageable as a tree of nodes with names, values, and data types. It's fundamental and universal...with one exception... ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
