Consistent ffi #22
Open
Consistent ffi #22
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
contiguity checking. all tests pass.
…llow for gcc-4.8 compatability
|
Seems like the first bullet above addresses #9 as well |
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.
This PR makes two main changes for consistent interfacing with C code, and error handling:
_ArrayWrapperclass, which always ensures arrays are the right type, and contiguous in memory (to avoid memory corruption). It also consistently handles passing single values to C routines.retcode != GSL_SUCCESS, an error is thrown in Python. This ensures that errors are always detected, and makes it possible to handle them explicitly in Python.