vsisimple: explicitly allow NULL in VSIFree and VSIRealloc #11378
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
2 tasks
lnicola
force-pushed
the
vsifree-null
branch
from
e05df6e
to
6acebb7
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.
What does this PR do?
It's not always clear if
freewrappers acceptnullptr, so let's explicitly document that it's allowed.Of course, I can update the PR if the intention is to forbid it in the future.
malloc(0)is even more problematic, but it's not addressed here.What are related issues/pull requests?
georust/gdal#589 (comment)
Tasklist
Environment
Provide environment details, if relevant: