I like the flip-flop operator as demo'd by Discipulus. If I don't use that, I often use the following pattern. The flip-flop operator maintains the state of whether you are inside the record or not - that's a very nice feature. Anyway, without the flip-flop, instead of maintaining a flag to tell me if I'm in the record or not, I call a subroutine to keep track of the "state". This may be a bit "wordy", but the logic is crystal clear (at least to me).
#!/usr/bin/perl
use strict;
use warnings;
while (defined (my $line = <DATA>))
{
process_record($line) if $line =~ /^\s*SCHEDULE "DUMMY CHECK"/;
}
sub process_record
{
my $line = shift; #the "trigger line"
print $line;
for (1..3) #maybe have regex for "end of record"?
{
my $line = <DATA>;
print $line;
}
print "\n"; #just a spacer
}
=prints
SCHEDULE "DUMMY CHECK"
DESCRIPTION "Do some stuff"
Check something
INTERVAL "10m"
SCHEDULE "DUMMY CHECK"
DESCRIPTION "Do some more stuff"
Check something
INTERVAL "30m"
=cut
__DATA__
SCHEDULE "TEST"
DESCRIPTION "Do Some stuff"
MINUTE "53"
HOUR "21"
SCHEDULE "DUMMY CHECK"
DESCRIPTION "Do some stuff"
Check something
INTERVAL "10m"
MINUTE "50"
HOUR "21"
SCHEDULE "TEST"
DESCRIPTION "Do Some stuff"
MINUTE "53"
HOUR "21"
SCHEDULE "DUMMY CHECK"
DESCRIPTION "Do some more stuff"
Check something
INTERVAL "30m"
MINUTE "50"
HOUR "21"
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|