[Bf-python] 64-bit and void*/int hackery
Ken Hughes
khughes at pacific.edu
Tue Feb 5 18:46:19 CET 2008
Martin Poirier wrote:
> --- Ken Hughes <khughes at pacific.edu> wrote:
>
>
>> When I was trying to make the code 64-bit clean a
>> few years ago that Ton was resistant to using intptr_t and uintptr_t:
>>
>>
>>
> http://lists.blender.org/pipermail/bf-committers/2005-November/012378.html
>
>> Not sure if I misunderstood why.
>>
>
> His point is valid for LP64 where you don't really
> have to use specially defined types.
Ok, so I still don't see his point. Aren't intptr_t and uintptr_t
"defined pointer-length types defined per platform" already? Or aren't
they C89 (or C90; whatever we are supposed to support, which we don't,
which is another separate issue) compliant? Maybe the issue is that the
current code is 64-bit compliant, so we should just ignore the warnings?
Ken
More information about the Bf-python
mailing list