From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Replace config file parser for "xl"
Date: Tue, 2 Mar 2010 21:29:04 +0000 [thread overview]
Message-ID: <4B8D8320.2000707@eu.citrix.com> (raw)
In-Reply-To: <19341.26082.271923.152094@mariner.uk.xensource.com>
On 02/03/10 19:24, Ian Jackson wrote:
> This provides a replacement config file parser for "xl" based on bison
> and flex.
>
> Benefits:
> * proper error reporting with line numbers
> * parser can understand nearly all "xm" configuration files directly
> (doesn't understand Python code but should do everything else)
> * parser also understands the ;-infested "xl" style files
> * removes the dependency on libconfig
> * better checking for certain kinds of mistakes
> * eliminates the strange "massage file and try again" code
>
> This is intended to support all config files currently supported by
> "xl" and almost all files supported by "xm". (NB that whether a
> feature works depends on the implementation of that feature in
> xl/libxl of course.)
>
> This patch also introduces a new library "libxlutil" which is mainly
> for the benefit of "xl". Users of libxl do not need to use libxlutil,
> but they can do so if they want to parse "xl" files without being
> "xl".
this is merely replacing a library dependency by a compilation
dependency, plus the burden on maintaining a ad-hoc grammar. At least it
would probably be useful to take the same approch as the linux kernel,
i.e. checking bison/flex output in the repository to account for bison
annoying volatility.
however since it's well separated from libxl,
Acked-by: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
--
Vincent
next prev parent reply other threads:[~2010-03-02 21:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 19:24 [PATCH] Replace config file parser for "xl" Ian Jackson
2010-03-02 21:29 ` Vincent Hanquez [this message]
2010-03-04 18:47 ` [PATCH] Fix config file interpretation when pci= not specified Ian Jackson
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=4B8D8320.2000707@eu.citrix.com \
--to=vincent.hanquez@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).