Update: Does "***Begin $subject" in the equality test need to be "***Begin $subject\n"?
So much to do here.
- #!/usr/bin/perl -w Warnings on.
- use strict; aid in debugging.
- use CGI; You'll get toasted for parsing $QUERY_STRING
- $| = 1; Let through whatever gets printed right away.
&dienice does nothing that
use CGI::Carp qw(fatalsToBrowser); can't do better.
Consider reading the file like this:
my $cgi = new CGI;
my $subject = $cgi->param('subject');
my @b;
{
local $/="***Begin Here***\n";
open INF, "< /full/path/to/postall.txt" or die $!;
@b = grep {
chomp; # remove "***Begin Here***\n", then
# remove marker and return true to grep if match
s/^\*\*\*Begin \Q$subject\E//;
} <INF>;
close INF or die $!;
}
# lines go by
for (@b) {
s/\n/<br\/>\n/g;
}
print @b;
Update2: Added chomp, positional ^, and comments to grep code, a litle text cleanup.
After Compline,
Zaxo
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.