[Python-Dev] Re: [Python-checkins] python/dist/src/Objects dictobject.c,2.127,2.128 floatobject.c,2.113,2.114 intobject.c,2.84,2.85 listobject.c,2.120,2.121 longobject.c,1.119,1.120 rangeobject.c,2.42,2.43 stringobject.c,2.169,2.170 tupleobject.c,2.69,2.70 typeobject.c,2.160,2.161 unicodeobject.c,2.155,2.156 xxobject.c,2.20,2.21

[Guido van Rossum]

> Can't provide you with that. I simply collect feedback from
> users having compile problems in that file.

Of course you never hear from users when their compiler is fixed so
that a particular work-around is no longer necessary, so you keep
collecting cruft until it collapses under its own weight.

> Note that most of these problems are related to declaring
> arrays as static forward (rather than C functions as Python
> normally does):

Note that staticforward was *only* intended for data declarations.  It
was never intended (nor needed) for functions.

> staticforward PyMethodDef mxODBCursor_Methods[];
> 
> ...tons of code...
> 
> statichere PyMethodDef mxODBCursor_Methods[] =
> {
>      /* DB API interface */
> ...
> 
> I could eliminate those by clever rearranging the code,
> but have never had an actual need for it.

You shouldn't need to.

I suggest that we keep Jeremy's checkins in 2.3.  Hopefully during the
alpha or beta release cycle we will find out if there *really* are
still platforms with broken compilers.  At worst, it will show up
after 2.3 final is released, and then we can fix it in 2.3.1.  You
won't have to target mx for 2.3 for another 18 months (assuming the
PBF ever releases Python-in-a-Tie).

--Guido van Rossum (home page: http://www.python.org/~guido/)