You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Introduce the ability to wrap UR features in pre-processor guards based
on the presence of the `guard: NAME` attribute in the yaml specs to
support conditionally enabling features.
Copy file name to clipboardExpand all lines: unified-runtime/scripts/YaML.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,7 @@ This document describes the YaML format used by the scripts for the API specific
22
22
* A header may take the following optional scalar fields: {`ordinal`, `version`}
23
23
-`ordinal` will be used to override the default order (alphabetical) in which regions appear in the specification; `default="1000"`. Multiple regions with the same ordinal will be ordered alphabetically.
24
24
-`version` can be used to define the minimum API version for all documents in the yml file; `default="1.0"`
25
+
-`guard` takes a name, which must be a valid C identifier, that will be used to generate pre-processor guards around feature code
-`version` will be used to define the minimum API version in which the macro will appear; `default="1.0"` This will also affect the order in which the macro appears within its section.
59
60
* A macro may take the following optional field which can be a scalar, a sequence of scalars or scalars to sequences: {`details`}
60
61
-`details` will be used as the macro's detailed comment
62
+
-`guard` takes a name, which must be a valid C identifier, that will be used to generate pre-processor guards around feature code
-`version` will be used to define the minimum API version in which the typedef will appear; `default="1.0"` This will also affect the order in which the typedef appears within its section and class.
150
152
* A typedef may take the following optional field which can be a scalar, a sequence of scalars or scalars to sequences: {`details`}
151
153
-`details` will be used as the typedef's detailed comment
154
+
-`guard` takes a name, which must be a valid C identifier, that will be used to generate pre-processor guards around feature code
@@ -344,6 +349,7 @@ plural form *enumerators* is abbreviated to `etors`.
344
349
+`version` will be used to define the minimum API version in which the etor will appear; `default="1.0"` This will also affect the order in which the etor appears within the enum.
345
350
* An enum may take the following optional field which can be a scalar, a sequence of scalars or scalars to sequences: {`details`}
346
351
-`details` will be used as the enum's detailed comment
352
+
-`guard` takes a name, which must be a valid C identifier, that will be used to generate pre-processor guards around feature code
0 commit comments