From 938ace69a0e112424a2f426a4881d1fd1fc922d2 Mon Sep 17 00:00:00 2001 From: Jeremy Hylton Date: Wed, 17 Jul 2002 16:30:39 +0000 Subject: 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. --- Python/ceval.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'Python/ceval.c') diff --git a/Python/ceval.c b/Python/ceval.c index 8c19787a52..0cd1c3623c 100644 --- a/Python/ceval.c +++ b/Python/ceval.c @@ -84,7 +84,7 @@ static long dxp[256]; #endif #endif -staticforward PyTypeObject gentype; +static PyTypeObject gentype; typedef struct { PyObject_HEAD -- cgit v1.2.1