You're thinking too hard. I cheated. My patch just fools the regex engine into thinking it hasn't actually started matching yet. Here's a drawn-out example.
$str = "abc.def.ghi.jkl";
$str =~ s{
.* # match as much as you can
\K # and then pretend HERE is where we start
\. .* # then a . and anything else
}{}x; # replace with nothing
__END__
abc.def.ghi.jkl $&
AAAAAAAAAAA .* "abc.def.ghi"
\K ""
B \. "."
BCCC .* ".jkl"
Does that help you see what I do? My patch consists of a couple lines of support, but this is the beef:
case KEEP:
PL_regstartp[0] = locinput - PL_bostr;
break;
That's what happens when the regex engine encounters the
\K. The rest of the patch is just creating the "KEEP" node, and telling
toke.c that "\K" is a valid escape sequence.
_____________________________________________________
Jeff[japhy]Pinyan:
Perl,
regex,
and perl
hacker, who'd like a job (NYC-area)
s++=END;++y(;-P)}y js++=;shajsj<++y(p-q)}?print:??;
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.