7stud

Considering your other post ( which might or might not have stemmed from this ) I thought I would update this thread with the final solution that I used ( also for anyone else who might care ).

I found that, considering {{Infobox was not the only chunk I needed, I was taking a huge performance hit. To avoid this I changed to a single sweep of the ( long ) text chunk as follows - I have removed the other parts that I extracted in the same sweep so as to stick to the OP topic. 

use strict   ;
use warnings ;

use Data::Dump qw( dump ) ;

my $text = <<'END_OF_STRING';
{{Infobox
 text text text
{{text text text
      text {{text text}}
  text}}
{{{text {{text }}
   text }}}
END}}
blah blah
blah blah
blah blah
{{Infobox
 text1 text1 text1 
{{text1 text1 text1 
      text1 {{text1 text1}}
  text1}} 
{{{text1 {{text1 }}
   text1 }}}
    }}
{{Infobox one}}
END_OF_STRING

my $box_contents = _get_info_boxes( $text ) ;
dump( $box_contents ) ;

exit;


sub _get_info_boxes { 

    my $text = shift ;
 

    my @info_box_contents          ;
    my $in_info_box                ;
    my $this_info_box_content = "" ;
    my $bracket_count = 0           ;
    foreach my $line ( split( /\n/, $text ) ) { 
    
    unless( $in_info_box ) { 
        next unless( $line =~ /{{Infobox/ ) ;
        $in_info_box   = 1              ;
    }

    $this_info_box_content .= $line . "\n" ;
    
    my $open_count  = ( $line =~ tr/{// ) ;
    my $close_count = ( $line =~ tr/}// ) ;
    
    $bracket_count = $bracket_count + $open_count - $close_count ;

    if( $bracket_count == 0 ) { 
        
        push @info_box_contents, $this_info_box_content ;
        $this_info_box_content = "" ;
        $in_info_box           =  0 ;
        $bracket_count         =  0 ;
    }
    

    }
    
    return \@info_box_contents ;

}

[download]

In reply to Re^2: RegEx - Positive Look-ahead by tmharish
in thread RegEx - Positive Look-ahead by tmharish

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.