mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Mike Beattie <>
Subject: [musl] Re: Bug: BOL/EOL anchors in regex capture groups won't match EOL
Date: Fri, 22 Jul 2022 14:02:38 +1200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, Jul 21, 2022 at 06:08:19PM +1200, Mike Beattie wrote:
> Removal of "^|" from the beginning of the trailing capture group:
>    $ ./r "(^|[,{}() ]|$)300([,{}() ]|$)" "0000 1111 2222"
>    regex: (^|[,{}() ]|$)300([,{}() ]|$)
>    regexec on [100 200 300]: Found

Please excuse the usage of "0000 1111 2222", that should be "100 200 300", I
was testing some much longer complex paths and regexes, but was distilling
the content of this report down to be as concise as possible.

I'm also not subscribed, please CC me on replies.

Mike Beattie <>

  reply	other threads:[~2022-07-22 11:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21  6:08 [musl] " Mike Beattie
2022-07-22  2:02 ` Mike Beattie [this message]
2022-08-03 22:43 ` Szabolcs Nagy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).