Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

should the headers include an extension version? #177

Open
bashbaug opened this issue Oct 2, 2021 · 0 comments
Open

should the headers include an extension version? #177

bashbaug opened this issue Oct 2, 2021 · 0 comments

Comments

@bashbaug
Copy link
Contributor

bashbaug commented Oct 2, 2021

Since we have started to include the extension version in the extension specs, should we include the extension version in the headers also? This will help applications to know what is the maximum version of the extension their headers support, vs. checking for the presence or absence of features that may be available only in newer versions of the extension individually.

This is done by some Khronos specs already. For example, the headers for a Vulkan extension include a line similar to:

#define VK_KHR_SURFACE_SPEC_VERSION       25

If we decide to do this, ideally we would include the version in the XML file and generate it in the headers (#113, #161).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant