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

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

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:??;

---

---

• 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.