From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NZm3m-0003a7-Ec for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:06:26 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NZm3h-0003WU-Gg for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:06:26 -0500 Received: from [199.232.76.173] (port=54980 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NZm3h-0003WJ-9x for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:06:21 -0500 Received: from e37.co.us.ibm.com ([32.97.110.158]:55189) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NZm3g-0006pe-PE for qemu-devel@nongnu.org; Tue, 26 Jan 2010 09:06:20 -0500 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e37.co.us.ibm.com (8.14.3/8.13.1) with ESMTP id o0QE4r11032137 for ; Tue, 26 Jan 2010 07:04:53 -0700 Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id o0QE6CoN089218 for ; Tue, 26 Jan 2010 07:06:12 -0700 Received: from d03av05.boulder.ibm.com (loopback [127.0.0.1]) by d03av05.boulder.ibm.com (8.14.3/8.13.1/NCO v10.0 AVout) with ESMTP id o0QE5scA012843 for ; Tue, 26 Jan 2010 07:05:54 -0700 Message-ID: <4B5EF6C1.2020105@linux.vnet.ibm.com> Date: Tue, 26 Jan 2010 08:05:53 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH] win32: use PRId64 instead of %lld References: <1264368221-3040-1-git-send-email-hpoussin@reactos.org> <20100125100905.GA9019@redhat.com> <20100125120348.461ce622@doriath> <20100125132719.23a483cf@doriath> <20100125153838.GB11161@redhat.com> <20100126094329.70719b6f@doriath> <4B5EE450.9090004@linux.vnet.ibm.com> <4B5EF45B.30001@redhat.com> In-Reply-To: <4B5EF45B.30001@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Markus Armbruster , "Michael S. Tsirkin" , Herve Poussineau , qemu-devel@nongnu.org, Luiz Capitulino On 01/26/2010 07:55 AM, Avi Kivity wrote: > The risk is that if we support a private extension (like '') and then > json is officially extended to support a conflicting or similar syntax > with a different meaning, then we cannot advance to the next revision > of json without breaking compatibility. The paragraph I quoted from the RFC seems to suggest that the authors of JSON boxed themselves in with respect to extending JSON. The reason being that a conforming implementation is given free reign to extend with "non-JSON forms or extensions". That would seem to prevent any extension. Keep in mind, JSON is a proper subset of ECMAScript which means the likelihood of extension going outside of ECMAScript would be extremely unlikely. I don't expect JSON is ever going to change. Regards, Anthony Liguori