From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:34208)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1RbZvP-0005bs-Df
	for qemu-devel@nongnu.org; Fri, 16 Dec 2011 10:42:20 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1RbZvJ-00071l-RC
	for qemu-devel@nongnu.org; Fri, 16 Dec 2011 10:42:19 -0500
Received: from mx1.redhat.com ([209.132.183.28]:37700)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1RbZvJ-00071U-IL
	for qemu-devel@nongnu.org; Fri, 16 Dec 2011 10:42:13 -0500
Message-ID: <4EEB66D0.7090006@redhat.com>
Date: Fri, 16 Dec 2011 16:42:08 +0100
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <1324036918-2405-1-git-send-email-pbonzini@redhat.com>	<1324036918-2405-2-git-send-email-pbonzini@redhat.com>	<4EEB4DE2.2060805@codemonkey.ws>	<4EEB4F0C.7050702@redhat.com>	<4EEB5152.2010405@codemonkey.ws>	<4EEB543C.5030104@redhat.com>	<4EEB59CE.809@codemonkey.ws>	<4EEB5A6D.4080705@redhat.com>	<4EEB5C11.5040907@codemonkey.ws>
	<4EEB5DD4.50302@redhat.com>	<4EEB5E52.7090204@codemonkey.ws>
	<4EEB600A.50803@redhat.com> <4EEB6278.6070401@codemonkey.ws>
In-Reply-To: <4EEB6278.6070401@codemonkey.ws>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH 1/8] qapi: fix NULL pointer dereference
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org

On 12/16/2011 04:23 PM, Anthony Liguori wrote:
> Ok.  I think nullable strings are not a good idea simply because it
> means that a property can have a state that cannot be set.

How is this different from NULL links?  (Honest, not trick question :)).

> Long term, I want to be able to do something like dump the current
> device graph to a config file, and then use that config file to recreate
> the same machine again.  A nullable property without a null
> representation would not allow this.

JSON null is such a representation.

Paolo