[Python-Dev] staticforward
Martin v. Loewis
martin@v.loewis.de
19 Jul 2002 18:09:40 +0200
- Previous message: [Python-Dev] staticforward
- Next message: [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
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
"M.-A. Lemburg" <mal@lemburg.com> writes:
> """
> Albert Chin-A-Young wrote on 2002-05-04:
> > >
> > > The AIX xlc ANSI compiler does not allow forward declaration of
> > > variables. This leads to a lot of problems with .c files that use
> > > staticforward (e.g. mxDateTime.c, mxProxy.c, etc.). Any chance of
> > > fixing these?
> """
>
> I'm not making this up.
Yes, but the user might be. I don't believe this statement is
factually correct - the compiler most certainly does allow forward
declaration of variables.
Also, such a statement is of little value unless associated with an
operating system release number (or better a compiler release number).
This conversation snippet indicates that the problem has not been
fully understood (atleast by Albert Chin-A-Young); solving an
incompletely-understood problem is a recipe for desasters, when it
comes to portability.
Regards,
Martin
- Previous message: [Python-Dev] staticforward
- Next message: [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
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]