summaryrefslogtreecommitdiffstats
path: root/Modules/md5module.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/md5module.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/md5module.c')
-rw-r--r--Modules/md5module.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/Modules/md5module.c b/Modules/md5module.c
index 045f27f..b7f2c69 100644
--- a/Modules/md5module.c
+++ b/Modules/md5module.c
@@ -17,7 +17,7 @@ typedef struct {
MD5_CTX md5; /* the context holder */
} md5object;
-staticforward PyTypeObject MD5type;
+static PyTypeObject MD5type;
#define is_md5object(v) ((v)->ob_type == &MD5type)