From: Markus Armbruster <armbru@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, wenchaoqemu@gmail.com
Subject: Re: [Qemu-devel] [PATCH] scripts: qapi-event.py: support vendor extension
Date: Thu, 10 Jul 2014 16:31:38 +0200 [thread overview]
Message-ID: <87fvi9i8tx.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <20140708141728.412a3f1c@redhat.com> (Luiz Capitulino's message of "Tue, 8 Jul 2014 14:17:28 -0400")
Luiz Capitulino <lcapitulino@redhat.com> writes:
> The event code generator barfs when it sees a dot in an event
> argument, this makes it impossible to support vendor extensions
> in event arguments as they always contain dots. Fix this by
> replacing dots by hyphens in the generated code.
Code replaces by underbar, not hyphen.
> PS: Event names and QMP command arguments may suffer from the
> same issue, but I'm not checking/fixing them today.
>
> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> ---
> scripts/qapi-event.py | 8 ++++----
> scripts/qapi.py | 4 ++++
> 2 files changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/scripts/qapi-event.py b/scripts/qapi-event.py
> index 601e307..485694b 100644
> --- a/scripts/qapi-event.py
> +++ b/scripts/qapi-event.py
> @@ -23,11 +23,11 @@ def _generate_event_api_name(event_name, params):
> if params:
> for argname, argentry, optional, structured in parse_args(params):
> if optional:
> - api_name += "bool has_%s,\n" % c_var(argname)
> + api_name += "bool has_%s,\n" % c_arg(argname)
> api_name += "".ljust(l)
>
> api_name += "%s %s,\n" % (c_type(argentry, is_param=True),
> - c_var(argname))
> + c_arg(argname))
> api_name += "".ljust(l)
>
> api_name += "Error **errp)"
> @@ -98,7 +98,7 @@ def generate_event_implement(api_name, event_name, params):
> ret += mcgen("""
> if (has_%(var)s) {
> """,
> - var = c_var(argname))
> + var = c_arg(argname))
> push_indent()
>
> if argentry == "str":
> @@ -113,7 +113,7 @@ def generate_event_implement(api_name, event_name, params):
> }
> """,
> var_type = var_type,
> - var = c_var(argname),
> + var = c_arg(argname),
> type = type_name(argentry),
> name = argname)
>
> diff --git a/scripts/qapi.py b/scripts/qapi.py
> index f2c6d1f..ddab14d 100644
> --- a/scripts/qapi.py
> +++ b/scripts/qapi.py
> @@ -434,6 +434,10 @@ def c_var(name, protect=True):
> def c_fun(name, protect=True):
> return c_var(name, protect).replace('.', '_')
>
> +# Should be used where vendor extensions are supported
> +def c_arg(name):
> + return c_var(name).replace('.', '_')
> +
> def c_list_type(name):
> return '%sList' % name
Can anybody think of a use of c_var() that needs '.' preserved?
next prev parent reply other threads:[~2014-07-10 14:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 18:17 [Qemu-devel] [PATCH] scripts: qapi-event.py: support vendor extension Luiz Capitulino
2014-07-09 15:43 ` [Qemu-devel] [PATCH for-2.1?] " Eric Blake
2014-07-09 16:08 ` Luiz Capitulino
2014-07-10 14:31 ` Markus Armbruster [this message]
2014-07-10 14:36 ` [Qemu-devel] [PATCH] " Luiz Capitulino
2014-07-11 14:42 ` Markus Armbruster
2014-07-11 15:38 ` Eric Blake
2014-07-11 16:01 ` Markus Armbruster
2014-07-11 18:51 ` Luiz Capitulino
2014-07-11 21:22 ` Eric Blake
2014-07-14 18:12 ` Luiz Capitulino
2014-07-14 18:31 ` Eric Blake
2014-07-14 18:32 ` Luiz Capitulino
2014-07-10 16:13 ` Eric Blake
2014-07-23 14:19 ` Wenchao Xia
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=87fvi9i8tx.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wenchaoqemu@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.