Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

proj_errno_reset: Also reset pj_errno #808

Merged
merged 1 commit into from
Feb 19, 2018

Conversation

Algunenano
Copy link
Contributor

Related to this PostGIS ticket. It has been temporarily solve by setting it manually after an error but I understand it was an unintended behaviour change and it should be handled here.

I've removed the postgis patch and applied this PR and the behaviour remains the same as with 4.9.3.

@kbevers
Copy link
Member

kbevers commented Feb 19, 2018

Yes, indeed it is unintended behaviour. The global error number within PROJ should be set with the new API functions as well. At least for now (we are probably changing error-handling in a later major version release). Thanks for finding and fixing this bug.

@kbevers kbevers merged commit efa636e into OSGeo:master Feb 19, 2018
kbevers added a commit to kbevers/PROJ that referenced this pull request Feb 23, 2018
The error number should not be reset until a new instance of "operation
..." is reached. The ignore-feature initially worked by accident since
pj_errno was not being reset when calling proj_errno_reset. This was
fixed in OSGeo#808, which subsequently caused ignored tests to fail.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants