From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=41331 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OFAqt-0000NL-PF for qemu-devel@nongnu.org; Thu, 20 May 2010 14:52:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OFAqr-00023v-Ld for qemu-devel@nongnu.org; Thu, 20 May 2010 14:52:15 -0400 Received: from mail-qy0-f173.google.com ([209.85.221.173]:38281) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OFAqr-00023h-H0 for qemu-devel@nongnu.org; Thu, 20 May 2010 14:52:13 -0400 Received: by qyk4 with SMTP id 4so161741qyk.18 for ; Thu, 20 May 2010 11:52:12 -0700 (PDT) Message-ID: <4BF584D8.1000108@codemonkey.ws> Date: Thu, 20 May 2010 13:52:08 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <1274303733-3700-1-git-send-email-lcapitulino@redhat.com> <1274303733-3700-3-git-send-email-lcapitulino@redhat.com> <4BF45BCF.5090300@codemonkey.ws> <20100520104433.1be3167c@redhat.com> <4BF55231.8020208@redhat.com> <4BF55A51.1080506@codemonkey.ws> <20100520132710.1e906771@redhat.com> <4BF56964.8030603@codemonkey.ws> <20100520154745.5b297d49@redhat.com> In-Reply-To: <20100520154745.5b297d49@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH 2/6] json-lexer: Handle missing escapes List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: Paolo Bonzini , qemu-devel@nongnu.org On 05/20/2010 01:47 PM, Luiz Capitulino wrote: > On Thu, 20 May 2010 11:55:00 -0500 > Anthony Liguori wrote: > > >> On 05/20/2010 11:27 AM, Luiz Capitulino wrote: >> >>> On Thu, 20 May 2010 10:50:41 -0500 >>> Anthony Liguori wrote: >>> >>> >>> >>>> On 05/20/2010 10:16 AM, Paolo Bonzini wrote: >>>> >>>> >>>>> On 05/20/2010 03:44 PM, Luiz Capitulino wrote: >>>>> >>>>> >>>>>> I think there's another issue in the handling of strings. >>>>>> >>>>>> The spec says that valid unescaped chars are in the following range: >>>>>> >>>>>> unescaped = %x20-21 / %x23-5B / %x5D-10FFFF >>>>>> >>>>>> >>>> That's a spec bug IMHO. Tab is %x09. Surely you can include tabs in >>>> strings. Any parser that didn't accept that would be broken. >>>> >>>> >>> Honestly, I had the impression this should be encoded as: %x5C %x74, but >>> if you're right, wouldn't this be true for other sequences as well? >>> >>> >> I don't think most reasonable clients are going to quote tabs as '\t'. >> > That would be a bug, wouldn't it? > Tabs are valid in JavaScript strings and I don't think it's reasonable to expect that a valid JavaScript string is not a valid JSON string. Regards, Anthony Liguori