Re^3: Named capture backreferences cannot be used in character classes?

in reply to Re^2: Named capture backreferences cannot be used in character classes?
in thread Named capture backreferences cannot be used in character classes?

"... I don't have a problem with it being "experimental"; as far as I have observed it hasn't changed in all the years it has been there ..."

When I read that this afternoon, that was my understanding too. However, poking aroung in perl5180delta some hours later (on a completely unrelated matter), I found: "/(?{})/ and /(??{})/ have been heavily reworked".

That's really just an FYI, if you're interested. It's still marked "experimental" and I saw nothing to indicate any specific performance enhancements.

-- Ken

Comment on Re^3: Named capture backreferences cannot be used in character classes?

Replies are listed 'Best First'.
Re^4: Named capture backreferences cannot be used in character classes? by BrowserUk (Patriarch) on Sep 27, 2013 at 13:43 UTC
That's really just an FYI, Thanks for the heads up. I haven't moved onto 5.18 yet, but I will be doing so soon. Thankfully, my primary use of the feature is where I have regex elements that are codependent. EG. `A => qr[...${B()}...], B => qr[...${C()}...], C => qr[...${A()}...],` [download] Which doesn't work because there is no way to order them such that all dependancies can be resolved at compile-time. Instead I have to use: `A => qr[...(??{B()})...], B => qr[...(??{C()})...], C => qr[...(??{A()})...],` [download] Which doesn't seem to be affected by the changes. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^4: Named capture backreferences cannot be used in character classes?
by BrowserUk (Patriarch) on Sep 27, 2013 at 13:43 UTC

That's really just an FYI,

Thanks for the heads up. I haven't moved onto 5.18 yet, but I will be doing so soon.

Thankfully, my primary use of the feature is where I have regex elements that are codependent. EG.

A => qr[...${B()}...],
B => qr[...${C()}...],
C => qr[...${A()}...],
[download]

Which doesn't work because there is no way to order them such that all dependancies can be resolved at compile-time.

Instead I have to use:

A => qr[...(??{B()})...],
B => qr[...(??{C()})...],
C => qr[...(??{A()})...],
[download]

Which doesn't seem to be affected by the changes.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom