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
* A handle requires the following scalar fields: {`desc`, `name`}
239
239
-`desc` will be used as the handles's description comment
240
240
-`name` must be a unique ISO-C standard identifier, start with `$` tag, be snake_case and end with `_handle_t`
241
-
* A handle may take the following optional scalar fields: {`class`, `alias`, `condition`, `ordinal`, `version`}
241
+
* A handle may take the following optional scalar fields: {`class`, `alias`, `condition`, `ordinal`, `version`, `loader_only`}
242
242
-`class` will be used to scope the handles declaration within the specified C++ class
243
243
-`alias` will be used to declare the handle as an alias of another handle; specifically, aliases in another namespace
244
244
-`condition` will be used as a C/C++ preprocessor `#if` conditional expression
245
245
-`ordinal` will be used to override the default order (in which they appear) the handles appears within its section; `default="1000"`
246
246
-`version` will be used to define the minimum API version in which the handles will appear; `default="1.0"` This will also affect the order in which the handles appears within its section.
247
+
-`loader_only` will be used to decide whether the handle can be instantiated and managed only by the loader.
247
248
* A handle may take the following optional field which can be a scalar, a sequence of scalars or scalars to sequences: {`details`}
248
249
-`details` will be used as the handle's detailed comment
0 commit comments