Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #18862 > unrolled thread

Re: Ctypes compatibility

Started byEvan Driscoll <edriscoll@wisc.edu>
First post2012-01-11 20:49 -0600
Last post2012-01-11 20:49 -0600
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Ctypes compatibility Evan Driscoll <edriscoll@wisc.edu> - 2012-01-11 20:49 -0600

#18862 — Re: Ctypes compatibility

FromEvan Driscoll <edriscoll@wisc.edu>
Date2012-01-11 20:49 -0600
SubjectRe: Ctypes compatibility
Message-ID<mailman.4673.1326336617.27778.python-list@python.org>

[Multipart message — attachments visible in raw view] — view raw

On 1/10/2012 22:42, Alec Taylor wrote:
> Use size_t
>
> http://en.wikipedia.org/wiki/C_data_types#Size_and_pointer_difference_types
Um, perhaps you misunderstand. I don't control the C API, I'm calling a
function that just exists in libc (unless I do what I said and write a
wrapper). If you're saying I should use c_size_t on the Python side, I
think that's outright wrong since I think some of the fields in the
dirent struct are 64 bits even on 32-bit systems. (I might be wrong
about that though.)

And even neglecting that, the types of the fields is only part of the
problem.

Evan


[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web