In the absence of being able to come up with a single line of code for regular expressions I've combined the split suggestions with a regular expression to achieve the desired result. Here is the working code:

my @section; my $i = -1; foreach (split /\n/, $str) { if (/^===Comments===$/) { ++$i; next; } next unless $i >= 0; $section[$i] .= "$_\n"; } my $comments1; my $comments2; my $comments3; if ($section[0] =~ /\n(.*?)=Microarray Data=/gs){ $comments1 = $1; } if ($section[1] =~ /\n(.*?)=Pathway Information=/gs){ $comments2 = $1; } if ($section[2] =~ /\n(.*?)=Aditional Info=/gs){ $comments3 = $1; } print $comments1, $comments2, $comments3;

Thanks for all pointers. If anyone can think of a way of making this neater and simpler that would be great. But otherwise it's working so I'm happy!

Thanks.


In reply to Re: Regular Expressions Challenge by danj35
in thread Regular Expressions Challenge by danj35

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.