Stowage/cpython
2
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-10-24 18:33:49 +00:00
Code Issues Projects Releases Packages Wiki Activity

SF bug [#456252] Python should never stomp on [u]intptr_t.

Browse source 
pyport.h:  typedef a new Py_intptr_t type.
    DELICATE ASSUMPTION:  That HAVE_UINTPTR_T implies intptr_t is
    available as well as uintptr_t.  If that turns out not to be
    true, things must get uglier (C99 wants both, so I think it's
    an assumption we're *likely* to get away with).
thread_nt.h, PyThread_start_new_thread:  MS _beginthread is documented
    as returning unsigned long; no idea why uintptr_t was being used.
Others:  Always use Py_[u]intptr_t, never [u]intptr_t directly.
This commit is contained in:
Tim Peters 2001-08-29 21:37:10 +00:00
parent 1936745668
commit 79248aa1e4
6 changed files with 22 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

2
Modules/socketmodule.c
View file

@ -1423,7 +1423,7 @@ PySocketSock_makefile(PySocketSockObject *s, PyObject *args)
char *mode = "r";
int bufsize = -1;
#ifdef MS_WIN32
intptr_t fd;
Py_intptr_t fd;
#else
int fd;
#endif