Re^5: Speeding up named capture buffer access

OKay, I can see what is driving your requirements. One possibility that might prove a little quicker is Alternative-capture-group-numbering*, which allows you to re-use capture numbering within different match alternatives.

The example given at the reference above is very pertinent to your use. It might at least be worth benchmarking.

*Unfortunately #anchors no longer seem to work at perldoc since they added that annoying moving menu :(

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.

RIP PCW It is as I've been saying!(Audio until 20090817)

Comment on Re^5: Speeding up named capture buffer access

Replies are listed 'Best First'.
Re^6: Speeding up named capture buffer access by SuicideJunkie (Vicar) on Dec 01, 2009 at 19:04 UTC
I'm using a dynamic width style override for perldoc, and the anchors work fine for me. (It also rearranges the sidebars and locks the floating bar to the top and generally squeezes out the unneeded fluff.) Your anchored link, for example, looks great to me How to make perldoc.perl.org resizable too!	[reply]
Re^7: Speeding up named capture buffer access by BrowserUk (Patriarch) on Dec 01, 2009 at 19:40 UTC
I don't use FF, and only go to perldoc when I want to post a reference as I have it all locally. Opera has a button() that just disables all the CSS which when clicked gives me a nice black on white, full width, basic html page with good size and readable fonts. But it does bug me when authors break basic html stuff, and force everyone else in the world to work out how to compensate, just so they can play a few stupid tricks and look 'hip'. It's just style over substance. ()It works wonder on many sites, microsoft, the beeb (though it can't correct for their insistance on using fixed width tabular formatting that only uses half of my screen). And many more are vastly more readable and useable after that simple click. I also get bugged by these little footnotes that show up: This page is best viewed in an up-to-date web browser with style sheets (CSS) enabled. While you will be able to view the content of this page in your current browser, you will not be able to get the full visual experience. Please consider upgrading your browser software or enabling style sheets (CSS) if you are able to do so. I don't go there for some art-fart's idea of a "full visual experience"--I go there to read the news! 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. RIP PCW It is as I've been saying!(Audio until 20090817)	[reply]
Re^6: Speeding up named capture buffer access by SBECK (Chaplain) on Dec 01, 2009 at 17:45 UTC
Good suggestion. I'm aware of them... I read up on them as I was learning about named buffers, but I quickly skipped them to the much nicer named buffers. However, I did NOT try to implement them. I'll spend some time looking at them as a possible compromise between the two.	[reply]