comment on

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
[download]

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

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks