Message 345340 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

In-reply-to
Author	vstinner
Recipients	vstinner
Date	2019年06月12日.13:17:33
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1560345453.67.0.201884543438.issue37250@roundup.psfhosted.org>

Content
"printfunc tp_print;" has been replaced with "Py_ssize_t tp_vectorcall_offset;": the type was basically a pointer and has been replaced with an integer. With "#define tp_print tp_vectorcall", "type->tp_print = NULL;" becomes "type->tp_vectorcall = NULL;". If -Werror is used, "type->tp_vectorcall = NULL;" would fail with a compilation error, since NULL is not exactly an integer, no? I'm not sure that it's an issue, I'm just thinking aloud.

Content

"printfunc tp_print;" has been replaced with "Py_ssize_t tp_vectorcall_offset;": the type was basically a pointer and has been replaced with an integer.
With "#define tp_print tp_vectorcall", "type->tp_print = NULL;" becomes "type->tp_vectorcall = NULL;".
If -Werror is used, "type->tp_vectorcall = NULL;" would fail with a compilation error, since NULL is not exactly an integer, no? I'm not sure that it's an issue, I'm just thinking aloud.

History
Date	User	Action	Args
2019年06月12日 13:17:33	vstinner	set	recipients: + vstinner
2019年06月12日 13:17:33	vstinner	set	messageid: <1560345453.67.0.201884543438.issue37250@roundup.psfhosted.org>
2019年06月12日 13:17:33	vstinner	link	issue37250 messages
2019年06月12日 13:17:33	vstinner	create

homepage