[Python-checkins] commit of r41623 - python/branches/ast-arena/Python/future.c
Neal Norwitz
nnorwitz at gmail.com
Tue Dec 6 09:54:20 CET 2005
On 12/6/05, Michael Hudson <mwh at python.net> wrote:
> "neal.norwitz" <python-checkins at python.org> writes:
>
> > Author: neal.norwitz
> > Date: Tue Dec 6 08:26:47 2005
> > New Revision: 41623
> >
> > Modified:
> > python/branches/ast-arena/Python/future.c
> > Log:
> > Reduce scope of feature
> >
> > Modified: python/branches/ast-arena/Python/future.c
> > ==============================================================================
> > --- python/branches/ast-arena/Python/future.c (original)
> > +++ python/branches/ast-arena/Python/future.c Tue Dec 6 08:26:47 2005
> > @@ -13,7 +13,6 @@
> > future_check_features(PyFutureFeatures *ff, stmt_ty s, const char *filename)
> > {
> > int i;
> > - const char *feature;
> > asdl_seq *names;
> >
> > assert(s->kind == ImportFrom_kind);
> > @@ -21,7 +20,7 @@
> > names = s->v.ImportFrom.names;
> > for (i = 0; i < asdl_seq_LEN(names); i++) {
> > alias_ty name = asdl_seq_GET(names, i);
> > - feature = PyString_AsString(name->name);
> > + const char *feature = PyString_AsString(name->name);
>
> This isn't C89, for the usual boring "code before declaration" reasons.
The line above is a declaration too (alias_ty name = ...) which is ok
AFAIK. Does it create a problem for some compiler?
n
More information about the Python-checkins
mailing list