qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Glauber Costa" <glommer@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 1/3] Modular command line options
Date: Fri, 23 May 2008 10:29:49 -0300	[thread overview]
Message-ID: <5d6222a80805230629u301fcc1cu7bdaeb25bc4dfb67@mail.gmail.com> (raw)
In-Reply-To: <48356BC4.3090805@web.de>

On Thu, May 22, 2008 at 9:49 AM, Jan Kiszka <jan.kiszka@web.de> wrote:
> Ian Jackson wrote:
>> Jan Kiszka writes ("[Qemu-devel] [PATCH 1/3] Modular command line options"):
>>> Following up on my earlier proposal to introduce per-machine command
>>> line options, this version provides a more generic approach. It should
>>> also be usable for scenarios like per-arch or per-accelerator.
>>
>> I approve of splitting the code up like this, and having a
>> table-driven parsing arrangement.  But ideally we could get rid of
>> `index' and the giant switch() statements too.  Something more like
>>
>>   typedef void QEMUOptionParser(struct QEMUOption *option, const char *optarg);
>>
>>   typedef struct QEMUOption {
>>       const char *name, *helpstring;
>>       QEMUOptionParser handler;
>>       int flags;
>
> Ack. This just enforces a bit more effort to convert the existing
> opts... :->
>
>>       int int_for_handler;
>>       void *void_for_handler;
>
> I don't think there is an need for both. A plain
>
>        void *parser_opaque;
>
> should suffice as the user can perfectly typecast the void to int.
>
>>   } QEMUOption;
>>
>>   qemu_register_option_set(const QEMUOption *options);
>
> Here I would then suggest
>
>        qemu_register_option_set(const char *set_name,
>                                 const QEMUOption *options);
>
> to save the chance for visually grouping options.

I don't follow the need for the set_name parameter. This should be in
the OptionSet structure.
You mean, joining two groups if they are registered with the same
name? This can be done by enforcing them to have
the same "name" parameter in the OptionSet structure. Am I failing to
understand anything here?

>
>
> Good idea. Then the structure should look like this:
>
> struct QEMUOptionSet {
>        const char *name;
          ^^^^^^^^^^^^


-- 
Glauber Costa.
"Free as in Freedom"
http://glommer.net

"The less confident you are, the more serious you have to act."

  reply	other threads:[~2008-05-23 13:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 23:51 [Qemu-devel] [PATCH 1/3] Modular command line options Jan Kiszka
2008-05-21 19:17 ` Glauber Costa
2008-05-21 20:58 ` Fabrice Bellard
2008-05-22 10:11   ` Ian Jackson
2008-05-22 10:19 ` Ian Jackson
2008-05-22 10:20   ` Ian Jackson
2008-05-22 12:49   ` [Qemu-devel] " Jan Kiszka
2008-05-23 13:29     ` Glauber Costa [this message]
2008-05-23 15:12       ` Jan Kiszka

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=5d6222a80805230629u301fcc1cu7bdaeb25bc4dfb67@mail.gmail.com \
    --to=glommer@gmail.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).