On 05/23/2010 01:03 PM, Jan Kiszka wrote:
Can your elaborate what precisely is ambiguous?
Can't the user choose the unique ID so that it aliases an unrelated
qtree path?
True. I'll swap the search order and document this. Qtree paths should
always rule.
Well, I guess the user could avoid ambiguity by avoiding /es.
I prefer having mutually exclusive 'path' and 'ref' arguments.
That would be unhandy.
Don't really see why.
I agree. This feature is very useful as a debugging aid, and as I don't
think we'll have debugging GUIs any time soon, it's better to defer the
problem until we really need to solve it.
I introduced .user_only as a monitor command tag and applied it on
device_show. But I also added the vmstate version to the device output,
maybe already helpful for users. All this will come with v3.
Thanks.
--
error compiling committee.c: too many arguments to function
