Re: [Qemu-devel] [PATCH v7 01/14] qapi: add 'if' to top-level expressions

[Markus Armbruster <armbru@redhat.com>]

Marc-André Lureau <marcandre.lureau@redhat.com> writes:

> Accept 'if' key in top-level elements, accepted as string or list of
> string type. The following patches will modify the test visitor to
> check the value is correctly saved, and generate #if/#endif code (as a
> single #if/endif line or a series for a list).
>
> Example of 'if' key:
> { 'struct': 'TestIfStruct', 'data': { 'foo': 'int' },
>   'if': 'defined(TEST_IF_STRUCT)' }
>
> The generated code is for now *unconditional*. Later patches generate
> the conditionals.
>
> A following patch for qapi-code-gen.txt will provide more complete
> documentation for 'if' usage.

Dropping this paragraph as per review of v6.

> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> Reviewed-by: Markus Armbruster <armbru@redhat.com>
[...]
> diff --git a/docs/devel/qapi-code-gen.txt b/docs/devel/qapi-code-gen.txt
> index 94a7e8f4d0..beca020575 100644
> --- a/docs/devel/qapi-code-gen.txt
> +++ b/docs/devel/qapi-code-gen.txt
> @@ -744,6 +744,28 @@ Example: Red Hat, Inc. controls redhat.com, and may therefore add a
>  downstream command __com.redhat_drive-mirror.
>  
>  
> +=== Configuring the schema ===
> +
> +Top-level QAPI expressions.  The value must be a string or a list of
> +string.  The corresponding generated code will then guard the inclusion
> +of that member in the larger struct or function with #if IFCOND
> +(or several #if lines for a list), where IFCOND is the value of the
> +'if' key.
> +
> +'struct', 'enum', 'union', 'alternate', 'command' and 'event'
> +top-level QAPI expressions can take an 'if' keyword like:
> +
> +{ 'struct': 'IfStruct', 'data': { 'foo': 'int' },
> +  'if': 'defined(IFCOND)' }
> +
> +Please note that you are responsible to ensure that the C code will
> +compile with an arbitrary combination of conditions, since the
> +generators are unable to check it at this point.
> +
> +The presence of 'if' keys in the schema is reflected through to the
> +introspection output depending on the build configuration.
> +
> +
>  == Client JSON Protocol introspection ==
>  
>  Clients of a Client JSON Protocol commonly need to figure out what

Replacing this hunk by

  +=== Configuring the schema ===
  +
  +The 'struct', 'enum', 'union', 'alternate', 'command' and 'event'
  +top-level expressions can take an 'if' key.  Its value must be a string
  +or a list of strings.  A string is shorthand for a list containing just
  +that string.  The code generated for the top-level expression will then
  +be guarded by #if COND for each COND in the list.
  +
  +Example: a conditional struct
  +
  + { 'struct': 'IfStruct', 'data': { 'foo': 'int' },
  +   'if': ['defined(CONFIG_FOO)', 'defined(HAVE_BAR)'] }
  +
  +gets its generated code guarded like this:
  +
  + #if defined(CONFIG_FOO)
  + #if defined(HAVE_BAR)
  + ... generated code ...
  + #endif /* defined(HAVE_BAR) */
  + #endif /* defined(CONFIG_FOO) */
  +
  +Please note that you are responsible to ensure that the C code will
  +compile with an arbitrary combination of conditions, since the
  +generators are unable to check it at this point.
  +
  +The presence of 'if' keys in the schema is reflected through to the
  +introspection output depending on the build configuration.
  +
  +

as per review of v6.

[...]