Movatterモバイル変換
[0]ホーム
More damage to intuition (was RE: [Python-Dev] Comparison of recursive objects)
Guido van Rossumguido@digicool.com
Mon, 22 Jan 2001 10:55:42 -0500
> Your faith in gcc is as charming as it is naive <wink>: the most> interesting cases of undefined behavior can't be checked no-way, no-how at> compile-time. That's why Barry keeps talking employers into dumping> thousands of dollars into a single Insure++ license. Insure++ actually tags> every pointer at runtime with its source, and gripes if non-equality> comparisons are done on a pair not derived from the same array or malloc> etc. Since Python type objects are individually allocated (not taken from a> preallocated contiguous vector), Insure++ should complain about that> compare.IMHO, *this* *particular* gripe of Insure++ is just a pain in thebutt, and I wish there was a way to turn it off in Insure++ withouthaving to fix the code.IMHO, this was included in the standard to allow segmented-memoryimplementations of C. Think certain DOS or Windows 3.1 memory modelswhere a pointer is a segment plus an offset. This is not currentpractice even on Palmpilots!The standard may say that such comparisons are undefined, but I don'tcare about this particular undefinedness, and I'm annoyed by therequired patches.--Guido van Rossum (home page:http://www.python.org/~guido/)
[8]ページ先頭