Mention restriction for accessing pgmptr#164
Merged
Merged
Conversation
added 2 commits
January 29, 2018 10:12
Mention entry point restriction on using _get_wpgmptr() - only for programs for wide entry points.
Mention entry point restriction on calling _get_pgmptr
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
2 participants
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.
The exports _get_pgmptr and _get_wpgmptr are only correct to use when a narrow or wide entry point is used, respectively. This is because the entry point determines whether the narrow or wide global variables are initialized. Adding this detail to the Remarks section of these two functions.