This will work as long as the brace that closes the env block is the last one. To wit: 

env {
   anything you want here
}
not-env {
   other stuff
}

[download]

is not going to work.

Now, it's possible that his input might look as simple as your example...but then he (hopefully) would have figured out a solution for that case already; something brain-dead like cat input | awk '{if (first == 1) {print l; l = $0;} else {first=1} }' for instance.

A poster above said it already -- if it nests, don't use regexes. Even if you do get it to work, you'll wish you hadn't.

---
"I hate it when I think myself into a corner."
Matt Mitchell

In reply to Re: Re: Parsing... possible w/o too much stress ? by antifun
in thread Parsing... possible w/o too much stress ? by spurperl

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.