|
From: | Paolo Bonzini |
Subject: | Re: [Qemu-devel] [PATCH 1/8] qapi: fix NULL pointer dereference |
Date: | Fri, 16 Dec 2011 16:03:48 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110930 Thunderbird/7.0.1 |
On 12/16/2011 03:56 PM, Anthony Liguori wrote:
I'd really prefer to stick to non-nullable strings as there is no obvious way to specify NULL in command line options.
We can leave it as the default. A property with a non-null default is implicitly not nullable, which actually makes some sense. We can model this in get_string/set_string too.
What are the uses of null in qdev string properties? I know you can't set a string to null since parse() doesn't have a null syntax. So we're really just talking about an uninitialized state, right?
Yes. No ROM BAR is an example of a NULL string property. Paolo
[Prev in Thread] | Current Thread | [Next in Thread] |