Update non-compliance version to allow definition checks #603
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem Statement
When using a definition check,
a preprocessor may evaluate an undefined macro to
0
. This means that the existing000
version for non-compliance is equivalent to the macro not being defined at all and yields the same result for#ifdef
.Solution
To enable the check for definition of the macro itself, meaning, provide different outputs for:
case and
// #define ONEMATH_BLAS_SPEC_VERSION // missing macro definition, may be 0
case, we need to use a number other than
0
.001
is hence proposed as the non-compliance version. It does not conflict with any existing release of the specification. As a natural extension, versions between001
and100
(Spec release 1.0), can be treated as alpha/beta and used as per special cases that can be defined later as and if needed.Thanks to @zettai-reido for detecting this issue.