[Python-bugs-list] [Bug #115051] Dodgy use of PyTuple_SET_ITEM in pyexpat.c

[noreply@sourceforge.net]

Bug #115051, was updated on 2000-Sep-21 22:33
Here is a current snapshot of the bug.

Project: Python
Category: Modules
Status: Closed
Resolution: Fixed
Bug Group: None
Priority: 5
Summary: Dodgy use of PyTuple_SET_ITEM in pyexpat.c

Details: CVS Python 2.0b1 (22 Sept) - Modules/pyexpat.c produces the following warning
when compiled, indicating dodgy use of PyTuple_SET_ITEM (testing return value, when it doesn't):
cc: Warning: ./pyexpat.c, line 425: In this statement, "0" of type "int", is being converted to "pointer to struct _object". (cvtdiftypes)
    if (PyTuple_SET_ITEM(arg, 0, bytes) < 0)
--------^

For context:

    if ((arg = PyTuple_New(1)) == NULL)
        goto finally;

    if (PyTuple_SET_ITEM(arg, 0, bytes) < 0)
        goto finally;

    if ((str = PyObject_CallObject(meth, arg)) == NULL)
        goto finally;


Follow-Ups:

Date: 2000-Sep-21 23:01
By: tim_one

Comment:
Fixed in rev 2.20.
-------------------------------------------------------

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=115051&group_id=5470