One reason that jumps out at me is that the pattern character, '.' won't normally match a newline.

If you append the '/s' modifier to your regexes it changes the behavior such that '.' will match newlines (see perlman:perlre). Try this:

if ( /if.*?\{/s .. /.*?\}.*?else/s ) {
  s/\{//;
  s/\}//;
}

[download]

This, of course, assumes that you have the entire if-else construct in $_ to begin with.

Update: fiddled with text.

Update 2: removed extraneous $_ bindings in substitutions and escaped the curly braces (nice catch, Zaxo).

dmm

You can give a man a fish and feed him for a day ...
Or, you can teach him to fish and feed him for a lifetime

In reply to Re: pattern matching by dmmiller2k
in thread pattern matching by sliles

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.