SWIG bindings for user_cb_data in repo::DownloadCallbacks, unit tests #1849
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
Unit tests for Python and Ruby implement the `BaseTestCase` class, which containsshared initialization code. This implements the `BaseTestCase` class for Perl unit tests.
There is no need to write initialization code in the tests. Instead, we can use the `BaseTestCase` class, just like in Python and Ruby tests.
In the C++ API, the user can return a pointer (void *) to user data in the `add_new_download` method of the `repo::DownlodCallbacks` class. This pointer is then passed as an argument to `void * user_cb_data` in other methods of the `repo::DownloadCallbacks` class. There was a problem of how to use this mechanism in SWIG bindings. I implemented and tested several solutions. In the case of passing a pointer, there was a problem with the ownership of the data the pointer points to. Users of Python and some other languages are used to the gargabe collector and automatically holding ownership of the passed data. While I've solved this for `user_cb_data`, passing another void pointer will need to be solved (I'll do that later). And from there, the ownership will be more complicated. We need the solution to work reliably in Python, Ruby and Perl. And possibly be easy to use for other languages in the future. In the end, I chose the method of passing an integer instead of a pointer. When passing an integer, there is no need to deal with who owns the number. The integer is passed by value. And if the user needs to pass objects, for example, he can create an array of objects and pass the index (integer) to the array. The array also provides ownership of the objects.
The `test_package_downloader` unit tests for C++, Python, Ruby, Perl now test passing `user_cb_data`. In the `test_repo` tests, the implementation of the `add_new_download` and `progress` methods has been intentionally removed to test functionality in case the library user does not implement these methods.
Merged
via the queue into
rpm-software-management:main
with commit Nov 18, 2024
dabead7
20 checks passed
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.
Closes: #1441
SWIG bindings for user_cb_data in
repo::DownloadCallbacksin the C++ API, the user can return a pointer (void *) to user data in theadd_new_downloadmethod of therepo::DownlodCallbacksclass. This pointer is then passed as an argument tovoid * user_cb_datain other methods of therepo::DownloadCallbacksclass.There was a problem of how to use this mechanism in SWIG bindings.
I implemented and tested several solutions. In the case of passing a pointer, there was a problem with the ownership of the data the pointer points to. Users of Python and some other languages are used to the gargabe collector and automatically holding ownership of the passed data. While I've solved this for
user_cb_data, passing another void pointer will need to be solved (I'll do that later). And from there, the ownership will be more complicated. We need the solution to work reliably in Python, Ruby and Perl. And possibly be easy to use for other languages in the future.In the end, I chose the method of passing an integer instead of a pointer. When passing an integer, there is no need to deal with who owns the number. The integer is passed by value. And if the user needs to pass objects, for example, he can create an array of objects and pass the index (integer) to the array. The array also provides ownership of the objects.
PR also improves and adds unit tests for Perl and extends unit tests for other languages.