Normally you will spend more time waiting for the disk delivering your data than parsing it. So the answer to question 2 would be that you shouldn't care. Better optimize for readability and maintainability

Parsing is a wide field. It might mean searching for a few strings or parsing a programming language like perl. I assume here that your parsing needs are rather simple

In that case you wouldn't need two processes. You would use two Finite-state_machines working in parallel:

 my $state1=0; my $state2=0;
 while ($record= $fp->getline())
        {
                $state1= statemachine1($state1,$record);
                $state2= statemachine2($state2,$record);
        }# end of while

[download]

Here is a short description and more links about finite state machines: Re^3: How to parse a text file.

UPDATE: Read your question again and if that file is just a long list of "records", i.e. lines without any structure that connects two or more lines, you don't even need a finite state machine. Just use the two subroutines. You do know about the split() function? Very helpful to split a line into its components

In reply to Re: passing a file content from one process to another process. by jethro
in thread passing a file content from one process to another process. by avanta

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.