Skip to content

Increase compiler warnings by default #568

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

Merged
merged 8 commits into from
Oct 13, 2023
Merged

Conversation

bradh352
Copy link
Member

c-ares was missing a couple of common compiler warnings during building that are widely recognized as a best practice. This PR makes no code changes, only build system changes to increase warning levels.

This PR does cause some new warnings to be emitted, a follow-up PR will address those.

Fix By: Brad House (@bradh352)

@bradh352 bradh352 requested a review from bagder October 10, 2023 16:30
@bradh352 bradh352 merged commit be8706c into c-ares:main Oct 13, 2023
@bradh352 bradh352 deleted the warnings branch October 13, 2023 10:46
bradh352 added a commit that referenced this pull request Oct 15, 2023
PR #568 increased the warning levels and c-ares code emitted a bunch of warnings. This PR fixes those warnings and starts transitioning internal data types into more proper forms (e.g. data lengths should be size_t not int). It does, however, have to manually cast back to what the public API needs due to API and ABI compliance (we aren't looking to break integrations, just clean up internals).

Fix By: Brad House (@bradh352)
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

Successfully merging this pull request may close these issues.

2 participants