Re: [Qemu-devel] Re: [PATCH 01/25] Introduce QEMU dictionary data type

[Avi Kivity]

On 07/29/2009 04:28 PM, Anthony Liguori wrote:
> > I'm worried about all those void *s as they move responsibility for 
> > type safety and lifecycle management to the user.  I'd much rather 
> > see a QObject (or Object) with the following methods:
> >
> >   clone() - deep copy an object; dicts will store copies so we'll 
> > avoid those leaks or a dictionary member modified after it was stored
> >   destroy()
>
>
> It probably would be just as easy to do a ref()/unref() such that the 
> deep copying was avoided.

Shallow copies have their own pitfalls, you put something in a dict and 
then modify it later.  I keep getting bitten by this in Python.  I guess 
we could live with it though.  The important thing is to have proper 
lifecycle management, which refcounting solves as well.

--
error compiling committee.c: too many arguments to function