JP Sugarbroad added the comment:
That matches our expectation. A subclass works - perhaps `c_void_p` could be
deprecated in favor of a built-in subclass for generic opaque pointers as well?
Glad you agree that a warning would be useful here
New submission from JP Sugarbroad :
The following code will likely crash on I32LP64 systems:
dim = lib.get_array_size(opaque)
ptrs = (c_void_p * dim)()
lib.get_array_values(opaque, ptrs)
for ptr in ptrs:
print(lib.get_object_value(ptr))
What happens is that `ptr` is not a `c_void_p
Change by JP Sugarbroad :
--
nosy: +taralx
___
Python tracker
<https://bugs.python.org/issue15994>
___
___
Python-bugs-list mailing list
Unsubscribe:
