Here's a single-pass alternative to this (uses the same test-vector set):

BEGIN { my %mask = ( q{"} => q{"***"}, q{'} => q{'***'}, ); my $connector = qr{ => | : }xms; sub elide { my ($key, # pattern: arm sensitive sub-string elision $string, ) = @_; $string =~ s{ ((?<! \\) ['"]) $key \g-1 \s* $connector \s* \K \g-1 ((?! \g-2 | \\) .)* (?: \\. (?2)*)* \g-2 } {$mask{$1}}xmsg; return $string; } } # end BEGIN block
Whether this variation is preferable is very much a matter of taste. The  BEGIN block is required so that certain scalars | lexicals (the  %mask hash in particular,  $connector not so much since it could easily be inlined) will be guaranteed to be properly initialized. Very much dependent on 5.10 regex extensions.


Give a man a fish:  <%-{-{-{-<


In reply to Re: Matching backslash in regexp negative lookbehind by AnomalousMonk
in thread Matching backslash in regexp negative lookbehind by 1nickt

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.