-
Notifications
You must be signed in to change notification settings - Fork 170
Semantics of p_c_pointer and PointerToCPtr #592
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
Comments
We can use |
Yes, we already do in |
I see. So just importing stuff from |
Yes, so callbacks cannot be done from CPython, I also just realized that, so we will simply not implement |
Currently
p_c_pointer(pointer(xi32), p)
gets translated to:and
p_c_pointer(xi64, p)
gets translated to:What should be the recommended usage? It seems to me the second case is incorrect, as
PointerToCPtr
should only accepts pointers as the first argument?The other issue is: we need to also have a CPython implementation of whatever syntax/semantics we choose. If it cannot be done for the above syntax, then we need to change it.
The text was updated successfully, but these errors were encountered: