Thanks for the reply's everbody!!!
While I was waiting for some answers I decided to forge on by myself. Obviously the ideas you guys gave me are better, and I will be incorporating them into my current code. For posterity though here is how I worked around:
#!/usr/bin/perl -w
#
my @BROKERS;
open (CONFIG, "ubroker.properties") || die "Can't Open ubroker file: $
+!";
while (<CONFIG>)
{
$/="";
next if /^#/;
if (/^\[UBroker\.WS\./)
{
push (@BROKERS,$_);
}
}
#chomp @BROKERS;
@FIRST=split(/\s+/,$BROKERS[1]);
#@SECOND=split(/\s+/,$BROKERS[2]);
#@THIRD=split(/\s+/,$BROKERS[3]);
#@FOURTH=split(/\s+/,$BROKERS[4]);;
foreach $i(@FIRST)
{
if ($i =~ /^initialSrvrInstance/i)
{
$max= $i;
print "$max\n";
}
}
close (CONFIG) || die "Can't Close ubroker file: $!";
exit 0;
But like you said I really like the entire hash approach better then what I am doing now!!!
Thanks for the Help!
Pat+
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.