Message236839
> see my old issue #17884
... and you can also re-read my explanations in that issue about why simply using uint32_t and int32_t doesn't work! We need something like PY_UINT32_T (and co) for portability.
The only part of #17884 that's still valid is that it may well make sense to insist that exact-width 32-bit and 64-bit signed and unsigned integer types are available when building Python. |
|
Date |
User |
Action |
Args |
2015-02-27 21:01:52 | mark.dickinson | set | recipients:
+ mark.dickinson, rhettinger, pitrou, vstinner, serhiy.storchaka |
2015-02-27 21:01:52 | mark.dickinson | set | messageid: <1425070912.79.0.00529237024579.issue23488@psf.upfronthosting.co.za> |
2015-02-27 21:01:52 | mark.dickinson | link | issue23488 messages |
2015-02-27 21:01:52 | mark.dickinson | create | |
|