Improve long handling for structs #1065
Merged
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
badcel
force-pushed
the
improve-long-handling
branch
from
defdfc2 to
a7761b9
Compare
On windows long has always 32 bit. On Unix it has 32 / 64 bit depending on the system architecture. This commit generates structs with a field of type "CLong" / "CULong" instead of "long" / "ulong" to match this behavior.
badcel
force-pushed
the
improve-long-handling
branch
from
a7761b9 to
31a2e20
Compare
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.
On windows long has always 32 bit. On Unix it has 32 / 64 bit depending on the system architecture.
This commit generates structs with a field of type "CLong" / "CULong" instead of "long" / "ulong" to match this behavior.
Fixes: #782