summaryrefslogtreecommitdiffstats
path: root/Modules/_tkinter.c
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>2000-06-30 15:01:00 (GMT)
committerFred Drake <fdrake@acm.org>2000-06-30 15:01:00 (GMT)
commita44d353e2b6d947d36ab9d36c1fc84335a0878fe (patch)
tree3d0add21fcb365aeeb5ac6b45add0a30e6f3b93b /Modules/_tkinter.c
parentd49e5b466731d0e68ea41655aecbe3a66b1976d9 (diff)
downloadcpython-a44d353e2b6d947d36ab9d36c1fc84335a0878fe.zip
cpython-a44d353e2b6d947d36ab9d36c1fc84335a0878fe.tar.gz
cpython-a44d353e2b6d947d36ab9d36c1fc84335a0878fe.tar.bz2
Trent Mick <trentm@activestate.com>:
The common technique for printing out a pointer has been to cast to a long and use the "%lx" printf modifier. This is incorrect on Win64 where casting to a long truncates the pointer. The "%p" formatter should be used instead. The problem as stated by Tim: > Unfortunately, the C committee refused to define what %p conversion "looks > like" -- they explicitly allowed it to be implementation-defined. Older > versions of Microsoft C even stuck a colon in the middle of the address (in > the days of segment+offset addressing)! The result is that the hex value of a pointer will maybe/maybe not have a 0x prepended to it. Notes on the patch: There are two main classes of changes: - in the various repr() functions that print out pointers - debugging printf's in the various thread_*.h files (these are why the patch is large) Closes SourceForge patch #100505.
Diffstat (limited to 'Modules/_tkinter.c')
-rw-r--r--Modules/_tkinter.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/Modules/_tkinter.c b/Modules/_tkinter.c
index da90559..d7a4fe1 100644
--- a/Modules/_tkinter.c
+++ b/Modules/_tkinter.c
@@ -1705,7 +1705,7 @@ Tktt_Repr(self)
TkttObject *v = (TkttObject *)self;
char buf[100];
- sprintf(buf, "<tktimertoken at 0x%lx%s>", (long)v,
+ sprintf(buf, "<tktimertoken at %p%s>", v,
v->func == NULL ? ", handler deleted" : "");
return PyString_FromString(buf);
}