Repository navigation
Allow imported function calls without the IAT_ prefix - #16
Merged
Merged
Conversation
…of "IAT_" or "__imp_" aliases anymore (Import Address Table). Updated samples to no longer use `IAT_` prefix.
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
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.
Imported functions can now be called using
call [MessageBoxA]after an#IMPORTdeclaration. ExistingIAT_and__imp_aliases remain compatibleand generate the same machine code.
Updated the samples and concatenation tutorial to use plain function names.
Ambiguous imports require a DLL-qualified alias, and conflicting local labels
produce an error.
Validation:
zcc.exeandzero.exe.IAT_calls still execute correctly.