KhronosGroup / KhronosGroup/Vulkan-Docs

XML misc enum issues

Open
#6 10 comments 0 reactions 0 assignees View on GitHub
Registry
Dominant language
JavaScript
Stars
3.3k
Forks
549
Avg merge
5d 5h
Merged PRs (30d)
2

Description

The following section of vk.xml has some issues if one was wanting to use the file to generate a binding for non C/C++ languages. Because the language target may not support it properly. Also technically it seems the LL extended literals came with C99 and C++11 so this _could_ be an issue even with the target language if you have some odd compiler maybe and you want to use C++03 and C89? Not certain on that though.

Plus its just weird that these values would need to be computed in C99/C++11 and up to get the proper value for them....

```
















```

Contributor guide

Open the contributing guide

Research direction

Start with the API Constants section shown from vk.xml and review the surrounding enum definitions and the comment thread for the intended representations. Determine what values should be emitted for non-C/C++ binding generation, then verify that the corrected constants preserve the Vulkan API values and avoid unsupported C/C++ literals.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, cpp, xml
Domain
api, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.