qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: jan.kiszka@siemens.com, dlaor@redhat.com, qemu-devel@nongnu.org,
	Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH 01/25] Introduce QEMU dictionary data type
Date: Wed, 29 Jul 2009 17:05:10 +0300	[thread overview]
Message-ID: <4A705716.9040209@redhat.com> (raw)
In-Reply-To: <4A704E99.9020107@us.ibm.com>

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

  reply	other threads:[~2009-07-29 14:00 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-28 22:04 [Qemu-devel] [PATCH 00/25] Monitor handlers new structure phase 1 Luiz Capitulino
2009-07-28 22:04 ` [Qemu-devel] [PATCH 01/25] Introduce QEMU dictionary data type Luiz Capitulino
2009-07-28 22:39   ` malc
2009-07-29 13:28     ` Luiz Capitulino
2009-07-29 13:38       ` malc
2009-07-29 13:38       ` Avi Kivity
2009-07-29 15:23         ` [Qemu-devel] " Paolo Bonzini
2009-07-29 15:24         ` Paolo Bonzini
2009-07-29  9:47   ` Avi Kivity
2009-07-29  9:49     ` Avi Kivity
2009-07-29 10:42       ` François Revol
2009-07-29 13:28     ` Anthony Liguori
2009-07-29 14:05       ` Avi Kivity [this message]
2009-07-29 13:46     ` Luiz Capitulino
2009-07-29 13:57       ` Avi Kivity
2009-07-29 14:22         ` Luiz Capitulino
2009-07-29 14:37           ` Avi Kivity
2009-07-29 16:11             ` Luiz Capitulino
2009-07-29 16:19               ` Avi Kivity
2009-07-30 14:50                 ` Luiz Capitulino
2009-07-30 15:03                   ` Avi Kivity
2009-07-30 15:05                     ` Luiz Capitulino
2009-07-30 15:04                   ` Filip Navara
2009-07-30 15:13                     ` Avi Kivity
2009-07-30 15:15                       ` Filip Navara
2009-07-30 15:19                       ` Paul Brook
2009-07-28 22:04 ` [Qemu-devel] [PATCH 02/25] net: Fix do_set_link() return type Luiz Capitulino
2009-07-28 22:04 ` [Qemu-devel] [PATCH 03/25] Add wrappers to functions used by the Monitor Luiz Capitulino
2009-07-28 22:04 ` [Qemu-devel] [PATCH 04/25] monitor: Document missing supported argument types Luiz Capitulino
2009-07-28 22:04 ` [Qemu-devel] [PATCH 05/25] monitor: New format for handlers " Luiz Capitulino
2009-07-28 22:04 ` [Qemu-devel] [PATCH 06/25] monitor: Setup a dictionary with handler arguments Luiz Capitulino
2009-07-28 22:04 ` [Qemu-devel] [PATCH 07/25] monitor: Export qemu-dict.h header Luiz Capitulino
2009-07-28 22:04 ` [Qemu-devel] [PATCH 08/25] monitor: New GET_TLONG and GET_TPHYSADDR macros Luiz Capitulino
2009-07-28 22:04 ` [Qemu-devel] [PATCH 09/25] monitor: Port handler_0 to use the dictionary Luiz Capitulino
2009-07-28 22:04 ` [Qemu-devel] [PATCH 10/25] monitor: Port handler_1 " Luiz Capitulino
2009-07-28 22:04 ` [Qemu-devel] [PATCH 11/25] monitor: Port handler_2 " Luiz Capitulino
2009-07-28 22:05 ` [Qemu-devel] [PATCH 12/25] monitor: Port handler_3 " Luiz Capitulino
2009-07-28 22:05 ` [Qemu-devel] [PATCH 13/25] monitor: Port handler_4 " Luiz Capitulino
2009-07-28 22:05 ` [Qemu-devel] [PATCH 14/25] monitor: Port handler_5 " Luiz Capitulino
2009-07-28 22:05 ` [Qemu-devel] [PATCH 15/25] monitor: Port handler_6 " Luiz Capitulino
2009-07-28 22:05 ` [Qemu-devel] [PATCH 16/25] monitor: Port handler_7 " Luiz Capitulino
2009-07-28 22:05 ` [Qemu-devel] [PATCH 17/25] monitor: Drop handler_8 and handler_9 handling Luiz Capitulino
2009-07-28 22:05 ` [Qemu-devel] [PATCH 18/25] monitor: Port handler_10 to use the dictionary Luiz Capitulino
2009-07-28 22:05 ` [Qemu-devel] [PATCH 19/25] monitor: Split monitor_handle_command() Luiz Capitulino
2009-07-29 15:31   ` [Qemu-devel] " Paolo Bonzini
2009-07-29 15:44     ` Luiz Capitulino
2009-07-28 22:05 ` [Qemu-devel] [PATCH 20/25] monitor: Add a new index for str_allocated[] Luiz Capitulino
2009-07-28 22:05 ` [Qemu-devel] [PATCH 21/25] monitor: Drop args[] from monitor_parse_command() Luiz Capitulino
2009-07-28 22:05 ` [Qemu-devel] [PATCH 22/25] monitor: Drop 'nb_args' " Luiz Capitulino
2009-07-28 22:05 ` [Qemu-devel] [PATCH 23/25] Add check support Luiz Capitulino
2009-07-28 22:05 ` [Qemu-devel] [PATCH 24/25] Introduce dictionary test data file Luiz Capitulino
2009-07-28 22:05 ` [Qemu-devel] [PATCH 25/25] Introduce qemu-dict unit-tests Luiz Capitulino

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A705716.9040209@redhat.com \
    --to=avi@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=dlaor@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).