diff options
author | Jeremy Hylton <jeremy@alum.mit.edu> | 2002-07-17 16:30:39 (GMT) |
---|---|---|
committer | Jeremy Hylton <jeremy@alum.mit.edu> | 2002-07-17 16:30:39 (GMT) |
commit | 938ace69a0e112424a2f426a4881d1fd1fc922d2 (patch) | |
tree | 29d42e42ec17a6ba2124b6fa36c3f00b23534413 /Objects/tupleobject.c | |
parent | 9cb64b954ae1bc3f0caeba98227de64cb6873026 (diff) | |
download | cpython-938ace69a0e112424a2f426a4881d1fd1fc922d2.zip cpython-938ace69a0e112424a2f426a4881d1fd1fc922d2.tar.gz cpython-938ace69a0e112424a2f426a4881d1fd1fc922d2.tar.bz2 |
staticforward bites the dust.
The staticforward define was needed to support certain broken C
compilers (notably SCO ODT 3.0, perhaps early AIX as well) botched the
static keyword when it was used with a forward declaration of a static
initialized structure. Standard C allows the forward declaration with
static, and we've decided to stop catering to broken C compilers. (In
fact, we expect that the compilers are all fixed eight years later.)
I'm leaving staticforward and statichere defined in object.h as
static. This is only for backwards compatibility with C extensions
that might still use it.
XXX I haven't updated the documentation.
Diffstat (limited to 'Objects/tupleobject.c')
-rw-r--r-- | Objects/tupleobject.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Objects/tupleobject.c b/Objects/tupleobject.c index 1a15bb7..add9cac 100644 --- a/Objects/tupleobject.c +++ b/Objects/tupleobject.c @@ -479,7 +479,7 @@ tuplerichcompare(PyObject *v, PyObject *w, int op) return PyObject_RichCompare(vt->ob_item[i], wt->ob_item[i], op); } -staticforward PyObject * +static PyObject * tuple_subtype_new(PyTypeObject *type, PyObject *args, PyObject *kwds); static PyObject * |