Should we backup this change? RE: Modifier substitutions.

["Andrej Borsenkow" <Andrej.Borsenkow@xxxxxxxxxxxxxx>]

There was no reply ... so I ask once more: should we backup this change?
I found, it can really be confusing (because pattern contents may be
pretty random).

I will rewrite _arguments/_configure (and may be a  bit doc) in this
case.

-andrej

> -----Original Message-----
> From: Andrej Borsenkow [mailto:Andrej.Borsenkow@xxxxxxxxxxxxxx]
> Sent: Thursday, April 06, 2000 1:33 PM
> To: Peter Stephenson; Zsh hackers list
> Subject: RE: Modifier substitutions.
>
>
>
> >
> > The `#' is being interpreted as an anchor at the head of the
> > string even
> > when buried inside $old.  I have a feeling that wasn't my intention.
> >
>
> Erm ... it was done by Bart (do not have arcticle number handy) as a
> result of my question. It was originally used when _configure called
> _long_options (was it called so?) to make "--disable-*" out of
> "--enable-*" (and vice versa). It gets pattern/replacement in the form
>
> '#--disable- --enable-'
> ...
>
> The intent was to not match string in the middle of option (it is
> unlikely in case of configure, but for the sake of generality
> ...) But,
> probably, now, with backreferences it can be rewrited as
>
> '(#m)--disable-(*) --enable-$MATCH'
>
> and explicitly anchor at the beginning.
>
> I do not insist on this change. This was the sole reason for it.
>
> -andrej
>
>