-
Notifications
You must be signed in to change notification settings - Fork 239
Convert all source code to C89 #81
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
Open
techflashYT
wants to merge
1
commit into
p2r3:main
Choose a base branch
from
techflashYT:c89
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In order to resolve the concern that p2r3 had about the default for most people needing to be C89 so that all future code is verified to be C89-compatible, if that's desired, I could suggest adding these arguments to the invocation of
cosmoccthat's currently in the GitHub Actions workflow of this repository, so that the officialcosmocctarget that's tested in GitHub Actions here would be able to fail the CI and print relevant errors in PRs that would accidentally add C89-incompatible code,but that's just my suggestion, not sure what p2r3 and other contributors would think of it. That idea would also be the most useful if GitHub Actions in this repo were eventually configured to test all PRs before merging and not only after merging, which it currently isn't, not sure if that's something p2r3 would think should be enabled or not.
bareiron/.github/workflows/build.yml
Lines 3 to 7 in b2aed79
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem with this is that, since C89 doesn't have
inline, it'll technically produce less efficient code. I hack around this with a bunch of#ifdef's to determine if the platform has any way to do inline functions, and if not, just stub out the keyword. But, for real "production-grade" builds, one would probably want to have inline function support (for however much difference it makes, probably not that much). I'm not against test-building it in strict C89 mode to ensure that nothing is catastrophically broken, but I'd probably advise against making it the default for final builds.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahh ok, I see, well in that case the solution is probably for there to be two builds in CI, an unoptimized C89-mode build (to test for C89 compatibility in CI) and an optimized C99+-mode build (to build any release binaries).
The project's code is very small and fast to compile in GitHub Actions, so two builds wouldn't bloat the CI time very much.