From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MzdEn-0005uS-Cn for qemu-devel@nongnu.org; Sun, 18 Oct 2009 17:24:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MzdEi-0005qL-UA for qemu-devel@nongnu.org; Sun, 18 Oct 2009 17:24:24 -0400 Received: from [199.232.76.173] (port=50493 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MzdEi-0005qI-I6 for qemu-devel@nongnu.org; Sun, 18 Oct 2009 17:24:20 -0400 Received: from mail-yw0-f176.google.com ([209.85.211.176]:42105) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MzdEh-0008LW-WD for qemu-devel@nongnu.org; Sun, 18 Oct 2009 17:24:20 -0400 Received: by ywh6 with SMTP id 6so3175809ywh.4 for ; Sun, 18 Oct 2009 14:24:17 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <4ADB514B.1070909@snarc.org> References: <1255037747-3340-1-git-send-email-lcapitulino@redhat.com> <4AD8E7B5.8000509@codemonkey.ws> <4AD910BA.4090607@gnu.org> <4AD922EB.5030501@codemonkey.ws> <4AD995FD.6070202@snarc.org> <20091018120631.0ab44d80@doriath> <4ADB2172.2040501@gnu.org> <4ADB2B13.4090207@codemonkey.ws> <4ADB41AE.8080103@codemonkey.ws> <4ADB514B.1070909@snarc.org> Date: Sun, 18 Oct 2009 16:24:17 -0500 Message-ID: Subject: Re: [Qemu-devel] Re: [PATCH 01/10] Introduce qmisc module From: Anthony Liguori Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vincent Hanquez Cc: Paolo Bonzini , qemu-devel@nongnu.org, Luiz Capitulino On Sun, Oct 18, 2009 at 12:32 PM, Vincent Hanquez wrote= : > Anthony Liguori wrote: >> >> Here's a first pass. =A0I'll clean up this afternoon and post a proper >> patch. =A0It turned out to work pretty well. > > It doesn't seems to validate anything ?? or is it just a lexer ? That's just a lexer. I posted a parser earlier. However, now I'm thinking I should update the parser to use the lexer. > you're also including ' as a string escape value (is that the single quot= e > thing you were talking about ?) which strikes me as invalid JSON. It's a compatible extension. We accept strings with those escapes but our encoder won't generate them. > -- > Vincent >