Paul and I have already been down that road :)
right now, until I figure out a better way I have another perl script that
forks several processes egrepping data out.
I call this script from within my other perl script to populate @output,
yeah I should use open.. maybe I will once I get things working and output
as it should. I am currently working on a non production, non enduser box
so I can suck up as much cpu/mem/resources as I care ;)
Ron
> -----Original Message-----
> From: Michael Fowler [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 21, 2001 3:27 PM
> To: Yacketta, Ronald
> Cc: Beginners (E-mail)
> Subject: Re: regex headache
>
>
> On Thu, Jun 21, 2001 at 02:58:02PM -0400, Yacketta, Ronald wrote:
> > foreach (@output) {
> > foreach my $test(@lookFor) {
> > $results{$test}++ if /$test/igo;
> > }
> >
> > this should create a hash etc.. etc..
> > to search for multiple words above (as you suggested?) I would
> >
> > $results{$test}++ if /$test/i && /failure/i;
>
> Ahh, I see. Then yes, that would be the proper adaptation.
> However, and
> someone may have already covered this with you, unless the file you're
> processing is guaranteed to always be small, sticking all of
> it into @output
> is probably not the best of ideas. If the output is that of
> a program,
> recall my examples of using open for a program and filtering
> the ouput.
>
>
> Michael
> --
> Administrator www.shoebox.net
> Programmer, System Administrator www.gallanttech.com
> --
>
