Comments on: Json Decoding Bug in Rails http://blog.inquirylabs.com/2007/05/21/json-decoding-bug-in-rails/ Politics, Programming and Possibilities Mon, 01 Dec 2008 22:44:42 +0000 http://wordpress.org/?v=2.6.1 By: carmen http://blog.inquirylabs.com/2007/05/21/json-decoding-bug-in-rails/#comment-15604 carmen Wed, 05 Sep 2007 06:18:15 +0000 http://blog.inquirylabs.com/2007/05/21/json-decoding-bug-in-rails/#comment-15604 the ruby+C JSON parser has serious issues, like not being able to parse anything thats not inside a [] and discarding it. im about to dig into the ragel since im sick of the slowness of the pure-ruby gem the ruby+C JSON parser has serious issues, like not being able to parse anything thats not inside a [] and discarding it. im about to dig into the ragel since im sick of the slowness of the pure-ruby gem

]]> By: Duane Johnson http://blog.inquirylabs.com/2007/05/21/json-decoding-bug-in-rails/#comment-9222 Duane Johnson Tue, 22 May 2007 01:26:43 +0000 http://blog.inquirylabs.com/2007/05/21/json-decoding-bug-in-rails/#comment-9222 True, it's not part of the JSON spec, but single-quoted strings *would* technically parse just fine when eval'ed in javascript---so maybe that's why the Rails parser (among others) is a little lenient there. True, it’s not part of the JSON spec, but single-quoted strings *would* technically parse just fine when eval’ed in javascript—so maybe that’s why the Rails parser (among others) is a little lenient there.

]]> By: Piers Cawley http://blog.inquirylabs.com/2007/05/21/json-decoding-bug-in-rails/#comment-9217 Piers Cawley Mon, 21 May 2007 22:46:20 +0000 http://blog.inquirylabs.com/2007/05/21/json-decoding-bug-in-rails/#comment-9217 Meanwhile, I've just been bitten by Ragel based JSON gem deciding that <code>{"title": "That\\'s great"}</code> is illegal despite the spec saying that any character may be escaped. Which would be fine if I had control over the feed, but I was trying to parse a del.icio.us.feed... The regular expression for matching a JSON string looks like this: /"((?:[^\x00-\x1f\\"]|\\(?:u[\da-fA-F]{4}|.))*)"/ It's not the most efficient variant that will do the match, but it'll serve. Unescaping the matched string is a little bit trickier, but, it's not really rocket science. I do wonder why the Rails even *cares* about single quotes in this context though; they don't appear to be legal string delimiters in the JSON spec. Meanwhile, I’ve just been bitten by Ragel based JSON gem deciding that {"title": "That\\'s great"} is illegal despite the spec saying that any character may be escaped. Which would be fine if I had control over the feed, but I was trying to parse a del.icio.us.feed…

The regular expression for matching a JSON string looks like this:

/”((?:[^\x00-\x1f\\"]|\\(?:u[\da-fA-F]{4}|.))*)”/

It’s not the most efficient variant that will do the match, but it’ll serve. Unescaping the matched string is a little bit trickier, but, it’s not really rocket science.

I do wonder why the Rails even *cares* about single quotes in this context though; they don’t appear to be legal string delimiters in the JSON spec.

]]>