From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MRTvt-0002G1-4R
	for qemu-devel@nongnu.org; Thu, 16 Jul 2009 12:35:45 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MRTvo-0002Bg-KD
	for qemu-devel@nongnu.org; Thu, 16 Jul 2009 12:35:44 -0400
Received: from [199.232.76.173] (port=39811 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MRTvo-0002BY-G1
	for qemu-devel@nongnu.org; Thu, 16 Jul 2009 12:35:40 -0400
Received: from gecko.sbs.de ([194.138.37.40]:17316)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <jan.kiszka@siemens.com>) id 1MRTvn-0001Oi-N1
	for qemu-devel@nongnu.org; Thu, 16 Jul 2009 12:35:40 -0400
Message-ID: <4A5F56D4.7050900@siemens.com>
Date: Thu, 16 Jul 2009 18:35:32 +0200
From: Jan Kiszka <jan.kiszka@siemens.com>
MIME-Version: 1.0
References: <1247756224-19219-1-git-send-email-kraxel@redhat.com>
	<1247756224-19219-5-git-send-email-kraxel@redhat.com>
In-Reply-To: <1247756224-19219-5-git-send-email-kraxel@redhat.com>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: [PATCH v3 4/5] QemuOpts: framework for storing and
 parsing options.
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org

Gerd Hoffmann wrote:
> This stores device parameters in a better way than unparsed strings.
> 
> New types:
>   QemuOpt       -  one key-value pair.
>   QemuOpts      -  group of key-value pairs, belonging to one
>                    device, i.e. one drive.
>   QemuOptsList  -  list of some kind of devices, i.e. all drives.
> 
> Functions are provided to work with these types.  The plan is that some
> day we will pass around QemuOpts pointers instead of strings filled with
> "key1=value1,key2=value2".

Will this also be able to handle the "-net <type>[,options=...]" special
case? Then it would be really great and could save us a lot of ugly code.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux