A hash might be nicer:

use strict;
use warnings;

my @strings = ('String A', 'String B', 'String C', 'String D', 'String
+ E');

my %string_handles = map { open my $fh, '>', "$_.log" or die "Couldn't
+ create '$_.log': $!"; $_ => $fh }
    @strings;

open (my $in_fh, '<', 'input.txt') or die "Couldn't open input file!\n
+";

local $/ = '';
while (my $paragraph = <$in_fh>) {
    while (my ($string, $out_fh) = each %string_handles)
    {
        next unless index($paragraph, $string) >= 0;
        print {$out_fh} $paragraph;
    }
}

close $in_fh;

[download]

In reply to Re^2: Parsing log file with blank lines for the field separator by chromatic
in thread Parsing log file with blank lines for the field separator by JasonJ

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.