Serhiy Storchaka added the comment:
Oh, I forgot to mention the issue number in commit messages. There are
changeset ad9b5c69b8b6 (for 3.3) and changeset 1f66fc397c8d (for default).
--
resolution: - fixed
stage: patch review - committed/rejected
status: open - closed
Changes by Serhiy Storchaka storch...@gmail.com:
--
assignee: - serhiy.storchaka
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16216
___
___
Changes by Jesús Cea Avión j...@jcea.es:
--
nosy: +jcea
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16216
___
___
Python-bugs-list mailing list
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16216
___
___
Python-bugs-list
Changes by Serhiy Storchaka storch...@gmail.com:
--
stage: - patch review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16216
___
___
Serhiy Storchaka added the comment:
The Standard is not guarantee that result of converting null pointer to integer
is zero or even it is a even number. I remember the ancient C implementation,
where it was not so (but Python is not supports these platform).
Of course, such a method of
New submission from Serhiy Storchaka:
In the function STRINGLIB(fastsearch_memchr_1char) in the file
Objects/stringlib/fastsearch.h NULL returned by memchr/memrchr casted to
intptr_t, then some arithmetic operations performed on this integer, and result
casted back to pointer. I think it is
STINNER Victor added the comment:
I think it is unsafe to do with NULL.
Could you please elaborate?
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16216
___
