qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] [PATCH] [RFC] Syncing documentation vs. -help vs. qemu_options table v2
@ 2009-03-16 19:23 Blue Swirl
  2009-03-16 19:38 ` Anthony Liguori
  2009-03-17  9:57 ` Avi Kivity
  0 siblings, 2 replies; 3+ messages in thread
From: Blue Swirl @ 2009-03-16 19:23 UTC (permalink / raw)
  To: qemu-devel

[-- Attachment #1: Type: text/plain, Size: 570 bytes --]

Hi,

I converted all options to the new system. Because of problems with #
and ' characters, I had to move from CPP to a Perl scripts. I'm sure
any Perl expert worth their salt could compress the scripts much
further. A comment token (HXCOMM?, deleted while parsing) would be
nice, then there could be comments that describe the syntax and usage
on top of options.hx.

Comments? Objections?

A related idea: maybe the machine definition files should also enclose
a mandatory TEXI description, leading to a generated list of machines
and their devices for qemu-doc.texi.

[-- Attachment #2: option_system.diff.bz2 --]
[-- Type: application/x-bzip2, Size: 21919 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Qemu-devel] [PATCH] [RFC] Syncing documentation vs. -help vs. qemu_options table v2
  2009-03-16 19:23 [Qemu-devel] [PATCH] [RFC] Syncing documentation vs. -help vs. qemu_options table v2 Blue Swirl
@ 2009-03-16 19:38 ` Anthony Liguori
  2009-03-17  9:57 ` Avi Kivity
  1 sibling, 0 replies; 3+ messages in thread
From: Anthony Liguori @ 2009-03-16 19:38 UTC (permalink / raw)
  To: qemu-devel

Blue Swirl wrote:
> Hi,
>
> I converted all options to the new system. Because of problems with #
> and ' characters, I had to move from CPP to a Perl scripts. I'm sure
> any Perl expert worth their salt could compress the scripts much
> further. A comment token (HXCOMM?, deleted while parsing) would be
> nice, then there could be comments that describe the syntax and usage
> on top of options.hx.
>
> Comments? Objections?
>   

Adding a perl dependency is really painful for win32.  We could check in 
the resulting options.h but if we can find a way to do it with CPP, that 
would be much better.

Long term, I think there are better ways to generate the man page.  For 
instance, if we had a verbose help setting, we could make use of 
help2man.  But I think this is a step in the right direction (provided 
we can drop the perl dependency).

Regards,

Anthony Liguori

> A related idea: maybe the machine definition files should also enclose
> a mandatory TEXI description, leading to a generated list of machines
> and their devices for qemu-doc.texi.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Qemu-devel] [PATCH] [RFC] Syncing documentation vs. -help vs. qemu_options table v2
  2009-03-16 19:23 [Qemu-devel] [PATCH] [RFC] Syncing documentation vs. -help vs. qemu_options table v2 Blue Swirl
  2009-03-16 19:38 ` Anthony Liguori
@ 2009-03-17  9:57 ` Avi Kivity
  1 sibling, 0 replies; 3+ messages in thread
From: Avi Kivity @ 2009-03-17  9:57 UTC (permalink / raw)
  To: qemu-devel

Blue Swirl wrote:
> Hi,
>
> I converted all options to the new system. Because of problems with #
> and ' characters, I had to move from CPP to a Perl scripts. I'm sure
> any Perl expert worth their salt could compress the scripts much
> further. A comment token (HXCOMM?, deleted while parsing) would be
> nice, then there could be comments that describe the syntax and usage
> on top of options.hx.
>   

The script needs expanding, not compressing.

-- 
error compiling committee.c: too many arguments to function

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-03-17  9:58 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-03-16 19:23 [Qemu-devel] [PATCH] [RFC] Syncing documentation vs. -help vs. qemu_options table v2 Blue Swirl
2009-03-16 19:38 ` Anthony Liguori
2009-03-17  9:57 ` Avi Kivity

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).