Always define CAML_NAME_SPACE
#10933
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
What is the point? |
|
It's not tested in the OCaml runtime, but it is tested in user C code (at least from a rapid grep) |
|
Ah, I wasn't expecting that. |
xavierleroy
approved these changes
Jan 30, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Small follow-up to #10863 inspired by the points being made at #10675 (comment).
Rather than obliterating
CAML_NAME_SPACE, we've made it the "default", so this just ensures inconfig.hthat it's always set (all the public headers pull inconfig.h). Apart from anything else, it ensures that it never gets used for anything else in OCaml 10 in another 25 years' time 馃檪