Treat .c files as C headers #345
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
denizzzka
changed the title
|
|
|
Test is coming soon |
atilaneves
approved these changes
Jun 11, 2024
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.
(Rare but useful case)
Standards isn't prohibit directive like
#include "c_file.c". But if included file is.cor.i(preprocessed file) it will allways be treated as C++ header by dpp.I planning to use this change to ease creating bindings by adding
-save-tempsflag into (almost any) C build environment and then processing obtained preprocessed files by dpp - so it helps to avoid of collecting of C compilation flags and passing all of them into dpp