On Fri, Feb 11, 2022 at 03:15:13PM +1100, raf <post...@raf.org> wrote:
> On Thu, Feb 10, 2022 at 07:08:14PM -0500, Viktor Dukhovni
> <postfix-us...@dukhovni.org> wrote:
>
> > > On 10 Feb 2022, at 7:03 pm, raf <post...@raf.org> wrote:
> > >
> > > Thanks, but I'm not sure that that is material to this
> > > issue.
> >
> > It is.
> >
> > > Even with regexp, x refers to "extended
> > > expression syntax".
> >
> > Which is a converse to "basic expression syntax", i.e. the obsolete
> > BRE syntax, in which "(" and "|" are ordinary characters unless escaped
> > "\(" or "\|", there is no support for "{n}" multiplicity or "+" for one
> > or more, ...
> >
> > > The extensions differ between
> > > regexp and pcre, but not to the extent that it would
> > > lead to that syntax error in that pattern (as far as
> > > I can see).
> >
> > Again, you're mistaken. Check the regex API manpages.
> >
> > --
> > Viktor.
>
> Thanks. That explains it.
But I still don't see why it was only the second
replacement index that was out of range, and not the
first as well.
cheers,
raf
