Switching to pure and clean C (+ Makefile isn't the best tool for this) #1
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
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.
Even though the suggested C code isn't optimized at its finest, it's much more readable.
One compilation unit for each part of the game, with a mix of functional and object oriented programming.
Comments in french might not be the best thing (
except if you're okay letting a baguette breach vulnerability in your code), I translated some of them.Also make might not be the best tool for this. I made a
bm.pyfile which seems to be more fitted for recompilation and optimization if the project grows. Using python let us make the output cleaner and have more control over how everything is managed when compiled/run.