[Bill Tutt] > Its definately for at least 32 bits. > Having a 32 bit specific type lets me not worry about all the issues > relating to: > What happens if sizeof(int) | sizeof(long) > 32 bits and I failed to > compensate for that somehow. Provided you're sticking to unsigned types, there should be few issues here: the behavior of C's unsigned ints is well-defined across platforms. > Now, the code that I changed to use the typedef might not care about this, > but other code using the typedef might. Just color me a paranoid SOB. :) > I'd rather always have a 32 bit type for something I know will always > require just 32 bits. Understood, but you can't have that, not in Python source. I'm -1 on the patch so long as it requires something that can't be had <wink>.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4