Hi Miyako, This morning I figured out more exactly where the error was occurring. It isn’t as general as I thought and it isn’t from .json files coming from disk. Instead, it was only occurring when using HTTP Get to pull down a .json file from a website.
I’m not sure if the web server should be doing something different or what, but the JSON that is received by HTTP Get has (always? sometimes?) a BOM at the beginning of it and that is what makes JSON Parse choke. -- Cannon.Smith Synergy Farm Solutions Inc. Hill Spring, AB Canada 403-626-3236 <can...@synergyfarmsolutions.com> <www.synergyfarmsolutions.com> > On Aug 31, 2017, at 4:12 PM, Keisuke Miyako via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > it's true that the commands were introduced to promote JSON, among other > things, but as long as you use "document to json" to restore the text, the > BOMs are removed anyway, so I can't see how the existence of a BOM could be > such a big problem. > > 2017/08/31 23:25、Cannon Smith via 4D_Tech <4d_tech@lists.4d.com> のメッセージ: > > The main reason I didn’t want to have a BOM character was that JSON Parse > chokes on such documents. I’ll file a bug for this. > ********************************************************************** 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:4d_tech-unsubscr...@lists.4d.com **********************************************************************
