Your markers look like they are fixed strings, so 

    if( $_ eq "--end foo--\n"){
    # . . .
    }

[download]
seems like a better test. Leave off "\n" if you chomp it.

A couple more approaches come to mind. If the file is not too big, you can abuse $/ to get the content in two gulps. 

my $interesting_bit;
{
    # maybe open here . . .
    local $/ = '--start foo--' . "\n";
    $interesting_bit = <FILE>;
    local $/ = '--end foo--' . "\n";
    $interesting_bit = <FILE>;
    # . . . and close here
}

[download]
That could burden memory.

A third way is similar to yours, but uses the flip-flop operator to condense the code. 

my $interesting_bit;
{
    # maybe open here . . .
    local $_;
    while (<FILE>) {
        if ($_ eq "--start foo--\n" .. $_ eq "--end foo--\n"  ) {
            $interesting_bit .= $_;
        }
        elsif ( $interesting_bit ) { last }
    }
    # . . . and close
}

[download]
This makes the same assumption about there being only one interesting bit. If the variable is populated while the flip-flop is false, we've run past the end marker and can quit reading.

I just noticed that I've changed the $interesting_bit variable from a flag in your code to an accumulator for the content. If you just set it true in the lhs of the flip-flop and do your processing in place of my .= operation, all will be well.

After Compline,
Zaxo

In reply to Re: Parsing Files for the Interesting Bit by Zaxo
in thread Parsing Files for the Interesting Bit by Cody Pendant

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.