e arguments. Instead of a shell function, we could
> > > also use:
> > >
> > > eval set x "${ac_configure_args}" && shift
> > > for option
> > > do
> > > [...]
> > > done
> > >
> > > ..., as done
e arguments. Instead of a shell function, we could
> > also use:
> >
> > eval set x "${ac_configure_args}" && shift
> > for option
> > do
> > [...]
> > done
> >
> > ..., as done in top-level c
args etc., but as the
> config-ml.in script is sourced in different contexts, it is not obvious
> to me that we're permitted to overwrite the shell's positional parameters
> here.
>
> OK for trunk? (Will properly indent scan_arguments before commit.)
>
> commit bc
el configure.ac for baseargs etc., but as the
config-ml.in script is sourced in different contexts, it is not obvious
to me that we're permitted to overwrite the shell's positional parameters
here.
OK for trunk? (Will properly indent scan_arguments before commit.)
commit bc6f99e98409
