[Python-Dev] Py_DECREF causes spurious gcc warning (original) (raw)
Delaney, Timothy C (Timothy) tdelaney at avaya.com
Wed Dec 17 18:39:48 EST 2003
- Previous message: open == file considered harmful (Re: [Python-Dev] RE: rexec.pyunuseable)
- Next message: [Python-Dev] Py_DECREF causes spurious gcc warning
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
From: Edward C. Jones
I use Gentoo 1.4 Linux with gcc 3.2.2. The C program given below gives the following compiler message: silly.c: In function
silly':_ _silly.c:5: warning: suggest explicit braces to avoid ambiguous
else' ----------------------- #include </usr/local/include/python2.3/Python.h> static PyObject* silly(PyObject* obj, PyObject *args) { if (1) PyDECREF(PyNone);
If I were you, I would pay attention to the warning.
I, of course, just added braces.
If you mean you changed it to:
static PyObject* silly(PyObject* obj, PyObject *args) { if (1) { Py_DECREF(Py_None); }
then I would say that's the right thing to do - all the time, in all code.
Tim Delaney
- Previous message: open == file considered harmful (Re: [Python-Dev] RE: rexec.pyunuseable)
- Next message: [Python-Dev] Py_DECREF causes spurious gcc warning
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]