Without having more test cases it is hard to know whether your regex will work as you intended. Sure the one stated here works for this case, but it works just as well if you replace
(?!.*<p>.*)
with
(?!.*<p>)
.

But I think you are missing the point of the assertion, as $1 now captures the second <p> in your string, and not the first, as the original had intended, which might not be important in this case, but might be in your understanding of what how better to approach regex problems) in which case:

/<p>.*?(<p> )(.+)(features\: <ul>)/i
or /[^(?:<p>)]+?(<p> )(.+)(features\: <ul>)/i works just as well. just because TMTOWTDI, doesn't mean that you have to use every tool in the toolshed to get to result when a simple screwdriver would have sufficed (pardon the expression).

-enlil


In reply to Re: Re: Lookahead assertion confusion by Enlil
in thread Lookahead assertion confusion by steves

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.