summaryrefslogtreecommitdiffstats
path: root/Modules/almodule.c
diff options
context:
space:
mode:
authorJeremy Hylton <jeremy@alum.mit.edu>2002-07-17 16:30:39 (GMT)
committerJeremy Hylton <jeremy@alum.mit.edu>2002-07-17 16:30:39 (GMT)
commit938ace69a0e112424a2f426a4881d1fd1fc922d2 (patch)
tree29d42e42ec17a6ba2124b6fa36c3f00b23534413 /Modules/almodule.c
parent9cb64b954ae1bc3f0caeba98227de64cb6873026 (diff)
downloadcpython-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 'Modules/almodule.c')
-rw-r--r--Modules/almodule.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/Modules/almodule.c b/Modules/almodule.c
index 05c4bef..8954528 100644
--- a/Modules/almodule.c
+++ b/Modules/almodule.c
@@ -24,7 +24,7 @@ typedef struct {
ALport port;
} alpobject;
-staticforward PyTypeObject Alptype;
+static PyTypeObject Alptype;
@@ -38,7 +38,7 @@ typedef struct {
ALconfig config;
} alcobject;
-staticforward PyTypeObject Alctype;
+static PyTypeObject Alctype;
static void