summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeremy Hylton <jeremy@alum.mit.edu>2002-07-17 16:30:39 +0000
committerJeremy Hylton <jeremy@alum.mit.edu>2002-07-17 16:30:39 +0000
commit938ace69a0e112424a2f426a4881d1fd1fc922d2 (patch)
tree29d42e42ec17a6ba2124b6fa36c3f00b23534413 /Modules/cmathmodule.c
parentSome modernization. Get rid of the redundant next() method. Always (diff)
downloadcpython-938ace69a0e112424a2f426a4881d1fd1fc922d2.tar.gz
cpython-938ace69a0e112424a2f426a4881d1fd1fc922d2.tar.bz2
cpython-938ace69a0e112424a2f426a4881d1fd1fc922d2.zip
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 'Modules/cmathmodule.c')
-rw-r--r--Modules/cmathmodule.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/Modules/cmathmodule.c b/Modules/cmathmodule.c
index 0437368de4c..5bb08f2913a 100644
--- a/Modules/cmathmodule.c
+++ b/Modules/cmathmodule.c
@@ -17,9 +17,9 @@ static Py_complex c_i = {0., 1.};
static Py_complex c_halfi = {0., 0.5};
/* forward declarations */
-staticforward Py_complex c_log(Py_complex);
-staticforward Py_complex c_prodi(Py_complex);
-staticforward Py_complex c_sqrt(Py_complex);
+static Py_complex c_log(Py_complex);
+static Py_complex c_prodi(Py_complex);
+static Py_complex c_sqrt(Py_complex);
static Py_complex