Odin binding generator script #207
Draft
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
monodop
force-pushed
the
binding-generators
branch
from
0cdc1fd to
73f30d1
Compare
|
Also for reference, here's what the extracted symbols looks like (from parser.py) https://gist.github.com/monodop/6875a1d677eb85212494e21025f4bff0 |
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.
I generalized my clay.h parser and wrote a generator for odin bindings. Ideally we could write different generators for different output bindings to reduce the amount of work needed to keep everything up to date. For odin, there's a pretty large number of weird exceptions and edge cases, so it might be worthwhile standardizing them.
This generator/parser might be more effort than it saves though, curious to hear thoughts about it.
Preview: https://gist.github.com/monodop/51b0c9430d3ca4807bb806e249877e19