A general rule of thumb is that a negative lookaround can never work if there is a .* or any other variable-length "general" pattern next to it. In your case, you have two such things, .* to the right and [^\n]+ to the left of (?!\sLib\s). You can easily check how Perl matched your strings against the regular expression by printing out the match variables:

while (<DATA>) { / ( #Start capture ( #Start Sub descript header '\*{20,} #start '------ delimiter (\n'[^\n]*?)+\n #middle of header '\*{20,}\n #end '------ delimiter )? #End Sub header (optional) (Private\s|Public\s|Friend\s)? #Scope (optional) (Static\s)? #Static (optional) (Sub\s|Function\s) #Sub or Function (mandatory) [^\n]+ #more stuff on same line (?!\sLib\s) #but not if Lib on line .* #and the rest of the file ) #End capture /sx and print "[$6/$7/$8]\n"; }; __DATA__ Private Declare Function DeleteFile Lib "kernel32" Alias "DeleteFileA" + _

One approach to make your parser more robust is to make it more specific, like explicitly parsing out the function/sub name and expecting (or rather, denying) the Lib keyword immediately after the function name:

while (<DATA>) { print; / ( #Start capture ( #Start Sub descript header '\*{20,} #start '------ delimiter (\n'[^\n]*?)+\n #middle of header '\*{20,}\n #end '------ delimiter )? #End Sub header (optional) (Private\s|Public\s|Friend\s)? #Scope (optional) (Static\s)? #Static (optional) (Sub\s|Function\s) #Sub or Function (mandatory) (\w+)\s+ # sub name ((?!Lib\s)) #no Lib on line ([^\n]+) #more stuff on same line unless "Lib" (.*) #and the rest of the file ) #End capture /sx and print "[$6/$7/$8]"; }; __DATA__ Private Declare Function DeleteFile Lib "kernel32" Alias "DeleteFileA"

To be a bit more specific about the word "general" above, a negative lookahead will never work if there is a variable length quantifier next to it with a pattern that will also match (parts of) the phrase you want to avoid.


In reply to Re: lookahead, lookbehind, ... I'm lost by Corion
in thread lookahead, lookbehind, ... I'm lost by ExReg

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.