It would be easier if the file content were stored in an array (or if, as suggested above, you were reading it one line at a time). Something like this -- with some of the initialization steps filled in -- could be worthwhile:
open( INPUT, "some.file" ) or die $!;
my @content;
{
local $/;
@content = split( /[\r\n+]/, <INPUT> );
}
my $tag1 = "whatever";
my $tag2 = "blah";
my $i = 0;
while ( $i < $#content ) { # don't test very last line
$_ = $content[$i++];
print "$content[$i]\n"
if (( /35=8/ and /$tag1/ and /$tag2/ ) or
( /35=9/ and /$tag1/ ));
}
I wanted to include the file open and read steps to show how to slurp it directly into an array (rather than slurping to a scalar then splitting to an array, which keeps two copies of the whole file in memory, which makes me itchy).
BTW, notice that you were using printf with a single scalar arg. Someday, if that string happened to contain "%d" or something similar, you might find the output to be different from what you intended.
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.