Fix incorrect error return values in CAPI #131
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
dbaston
force-pushed
the
fix-capi-return-code
branch
from
bc82a24
to
bfe6b8b
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.
In some cases, the CAPI function
GEOSLength_rreturns2on error, when it is documented to return0. The2is likely to be interpreted as "success" by a caller.In some cases, the CAPI function
GEOSIsValidDetail_rreturns0on error, when it is documented to return2. The0would be falsely interpreted as "geometry invalid."Trac ticket https://trac.osgeo.org/geos/ticket/941#ticket