From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JwIT1-0000UB-TE for qemu-devel@nongnu.org; Wed, 14 May 2008 11:00:31 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JwIT0-0000TR-AL for qemu-devel@nongnu.org; Wed, 14 May 2008 11:00:31 -0400 Received: from [199.232.76.173] (port=59844 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JwIT0-0000TL-05 for qemu-devel@nongnu.org; Wed, 14 May 2008 11:00:30 -0400 Received: from e1.ny.us.ibm.com ([32.97.182.141]:60991) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JwISy-00006G-Kv for qemu-devel@nongnu.org; Wed, 14 May 2008 11:00:28 -0400 Received: from d01relay06.pok.ibm.com (d01relay06.pok.ibm.com [9.56.227.116]) by e1.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id m4EF0Oxo024022 for ; Wed, 14 May 2008 11:00:24 -0400 Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d01relay06.pok.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id m4EF0Eju1237136 for ; Wed, 14 May 2008 11:00:16 -0400 Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m4EExqp1027825 for ; Wed, 14 May 2008 08:59:53 -0600 Message-ID: <482AFE66.5060407@us.ibm.com> Date: Wed, 14 May 2008 09:59:50 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [kvm-devel] [PATCH] Add support for a configuration file References: <1210713545-11916-1-git-send-email-aliguori@us.ibm.com> <482A1F1C.2020902@codemonkey.ws> <20080513232021.GA8844@redhat.com> <482AFA1C.3030800@qumranet.com> In-Reply-To: <482AFA1C.3030800@qumranet.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org, Paul Brook Avi Kivity wrote: > Daniel P. Berrange wrote: >> That's very nearly YAML format[1], which is attractive because parsers >> are available in every major programming language, and it is still >> pretty human friendly. >> >> So my preference would be to go with the last option and make sure >> it really is YAML compliant so people can use standard tools for >> generating and parsing the format. >> > > Using a standard format has the added benefit that things like quoting > are taken care of. > > Filenames with leading and trailing spaces, anyone? Embedded control > characters? YAML is a bad choice though. It's purpose is to model data structures of embedded languages (similar to JSON). The syntax would get out of hand quickly because what we've been talking about so far would be modeled as an association whereas semantically, we want it to be a sequence. To make it a sequence, we would have to prefix every line with '-'. I'm not against following some sort of standard (or even best practice). I just don't like YAML. Regards, Anthony Liguori