mirror of
https://github.com/Motorhead1991/qemu.git
synced 2025-08-05 08:43:55 -06:00
qapi: Add feature flags to enum members
This is quite similar to commit 84ab008687
"qapi: Add feature flags to
struct members", only for enums instead of structs.
Special feature flag 'deprecated' is silently ignored there. This is
okay only because it will be implemented shortly.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Message-Id: <20211025042405.3762351-3-armbru@redhat.com>
Reviewed-by: John Snow <jsnow@redhat.com>
This commit is contained in:
parent
75ecee7262
commit
b6c18755e4
13 changed files with 57 additions and 14 deletions
|
@ -200,7 +200,9 @@ Syntax::
|
|||
'*if': COND,
|
||||
'*features': FEATURES }
|
||||
ENUM-VALUE = STRING
|
||||
| { 'name': STRING, '*if': COND }
|
||||
| { 'name': STRING,
|
||||
'*if': COND,
|
||||
'*features': FEATURES }
|
||||
|
||||
Member 'enum' names the enum type.
|
||||
|
||||
|
@ -706,8 +708,10 @@ QEMU shows a certain behaviour.
|
|||
Special features
|
||||
~~~~~~~~~~~~~~~~
|
||||
|
||||
Feature "deprecated" marks a command, event, or struct member as
|
||||
deprecated. It is not supported elsewhere so far.
|
||||
Feature "deprecated" marks a command, event, enum value, or struct
|
||||
member as deprecated. It is not supported elsewhere so far.
|
||||
Interfaces so marked may be withdrawn in future releases in accordance
|
||||
with QEMU's deprecation policy.
|
||||
|
||||
|
||||
Naming rules and reserved names
|
||||
|
@ -1157,7 +1161,8 @@ and "variants".
|
|||
|
||||
"members" is a JSON array describing the object's common members, if
|
||||
any. Each element is a JSON object with members "name" (the member's
|
||||
name), "type" (the name of its type), and optionally "default". The
|
||||
name), "type" (the name of its type), "features" (a JSON array of
|
||||
feature strings), and "default". The latter two are optional. The
|
||||
member is optional if "default" is present. Currently, "default" can
|
||||
only have value null. Other values are reserved for future
|
||||
extensions. The "members" array is in no particular order; clients
|
||||
|
@ -1234,7 +1239,8 @@ The SchemaInfo for an enumeration type has meta-type "enum" and
|
|||
variant member "members".
|
||||
|
||||
"members" is a JSON array describing the enumeration values. Each
|
||||
element is a JSON object with member "name" (the member's name). The
|
||||
element is a JSON object with member "name" (the member's name), and
|
||||
optionally "features" (a JSON array of feature strings). The
|
||||
"members" array is in no particular order; clients must search the
|
||||
entire array when learning whether a particular value is supported.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue