zsh-workers
 help / color / mirror / code / Atom feed
From: Stephane Chazelas <stephane@chazelas.org>
To: Oliver Kiddle <opk@zsh.org>
Cc: Zsh workers <zsh-workers@zsh.org>
Subject: named capture groups with PCRE matching (Was: PATCH: migrate pcre module to pcre2)
Date: Sat, 6 May 2023 05:44:45 +0100	[thread overview]
Message-ID: <20230506044445.4bzhi7zpllwtcen2@chazelas.org> (raw)
In-Reply-To: <81584-1683329746.147485@6Tk5.mCsC.BbNC>

2023-05-06 01:35:46 +0200, Oliver Kiddle:
[...]
> When looking at PCRE documentation for this, other ideas for extensions
> I saw would be to support:
> 
>  * named capture groups
>    (either to an associative array or to variables directly?)
[...]

I was thinking about that when answering
https://unix.stackexchange.com/questions/742664/bash-posix-regex-optional-groups/742680#742680
recently.

Maybe we could do:

typeset -A match
if [[ aa =~ '(?<foo>.)(?<bar>)' ]]
  print -r -- $match[foo] $match[bar]

That is if $match is an associative array, store the named
capture groups there. Same for pcre_match -a array (or add a -A
assoc there)

There's the question of $mbegin / $mend. Should all three
$match, $mbegin and $mend be automatically converted to assoc if
any of them is an assoc?

-- 
Stephane


  reply	other threads:[~2023-05-06  4:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-05 23:35 PATCH: migrate pcre module to pcre2 Oliver Kiddle
2023-05-06  4:44 ` Stephane Chazelas [this message]
2023-05-06 18:56   ` named capture groups with PCRE matching (Was: PATCH: migrate pcre module to pcre2) Bart Schaefer
2023-05-06 23:06     ` Oliver Kiddle
2023-05-10 23:26 ` PATCH: migrate pcre module to pcre2 Oliver Kiddle
2023-05-12 23:12 ` Phil Pennock
2023-05-24 18:11   ` Oliver Kiddle
2023-06-13  7:35 ` Jun T
2023-06-19  8:20   ` Jun T

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=20230506044445.4bzhi7zpllwtcen2@chazelas.org \
    --to=stephane@chazelas.org \
    --cc=opk@zsh.org \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.vuxu.org/mirror/zsh/

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).