The "most efficient" method would depend on what you're going to do with the lines that don't match. If you're going to be splitting them into fields, then you might as well split the line first and check the userid with a simple eq:

while(<$file>){ my @fields = split ':'; last if $fields[0] eq $userid; }

But if you're not doing that, then it's probably more efficient to leave the line as it is and do a simple regex check:

while(<$file>){ last if /^$userid:/; # do whatever }

One more note: if there's any chance that the userid field (or perhaps other fields) could contain colons, either escaped or quoted, you should probably use a module like Text::CSV to handle that properly.

Aaron B.
Available for small or large Perl jobs and *nix system administration; see my home node.


In reply to Re: Most Efficient Way to match this by aaron_baugher
in thread Most Efficient Way to match this by jmneedhamco

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.