diff Python/thread_nt.h @ 19568:b0f5278a2ab4 legacy-trunk

SF bug [#456252] Python should never stomp on [u]intptr_t. 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.
author Tim Peters <tim.peters@gmail.com>
date Wed, 29 Aug 2001 21:37:10 +0000
parents 6f6f965c5e2d
children ebfd87e87884
line wrap: on
line diff
--- a/Python/thread_nt.h	Wed Aug 29 20:57:43 2001 +0000
+++ b/Python/thread_nt.h	Wed Aug 29 21:37:10 2001 +0000
@@ -152,7 +152,7 @@
  */
 int PyThread_start_new_thread(void (*func)(void *), void *arg)
 {
-	uintptr_t rv;
+	unsigned long rv;
 	int success = 0;
 
 	dprintf(("%ld: PyThread_start_new_thread called\n", PyThread_get_thread_ident()));
@@ -161,7 +161,7 @@
 
 	rv = _beginthread(func, 0, arg); /* use default stack size */
  
-	if (rv != -1) {
+	if (rv != (unsigned long)-1) {
 		success = 1;
 		dprintf(("%ld: PyThread_start_new_thread succeeded: %p\n", PyThread_get_thread_ident(), rv));
 	}