Skip to content
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

Fix build with GCC 15 #183

Merged
merged 1 commit into from
Jan 22, 2025
Merged

Conversation

yselkowitz
Copy link
Contributor

C23 changes the implication of a function declaration without arguments from an undetermined number and type to void (no arguments). While that is true in most of the cases here, init() and destroy() actually take a settings_t*. This defines the arguments (or lack thereof) of all functions, avoiding any ambiguity.

https://gcc.gnu.org/gcc-15/porting_to.html

@christophgysin
Copy link
Owner

Thanks! Can you rebase this on top of latest master, so the CI checks pass?

C23 changes the implication of a function declaration without arguments
from an undetermined number and type to `void` (no arguments).  While that
is true in most of the cases here, init() and destroy() actually take a
settings_t*.  This defines the arguments (or lack thereof) of all
functions, avoiding any ambiguity.

https://gcc.gnu.org/gcc-15/porting_to.html
@yselkowitz
Copy link
Contributor Author

Done; all tests now pass.

@christophgysin christophgysin merged commit 9883809 into christophgysin:master Jan 22, 2025
13 checks passed
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