KhronosGroup / KhronosGroup/Vulkan-Docs
vk.xml's `define` category no longer restricted to actual #defines
Open
Feature Request
Registry
Resolving Inside Khronos
- Dominant language
- JavaScript
- Stars
- 3.3k
- Forks
- 549
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 2
Description
Vulkan 1.1 added the following to vk.xml:
struct ANativeWindow;
This is not a `#define`, yet it uses the `define` category. It ought to be a `basetype` (not that that would make processing it easier). I imagine `define` was used because it worked, because the C and C++ generators just dump whatever is in a `define` category without processing it.
If the idea is that `define` is just "random C/C++ stuff", then that should probably be well-stated in the documentation. But at present, all it says is "`define` (macro `#define` directives)".
Contributor guide
Assessment
This issue has not been assessed yet.