This repository has been archived by the owner on Jan 8, 2025. It is now read-only.
No errors on deprecated warnings #118
Open
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
Since some features are deprecated (and more possibly will be eventually), keep errors on warnings (-Werror) but also add an exception to just warn on deprecation (-Wno-error=deprecated) rather than fail. This keeps deprecation warnings visible and also causes more serious warnings (like uninitialized variables/pointers) to error. This addresses issue DDMAL#110.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Since some features are deprecated (and more possibly will be
eventually), keep errors on warnings (-Werror) but also add an exception
to just warn on deprecation (-Wno-error=deprecated) rather than fail.
This keeps deprecation warnings visible and also causes more serious
warnings (like uninitialized variables/pointers) to error.
This addresses issue #110.