Also in the chatterbox, I pointed out File::Basename and File::Spec to you. Both will only work for your filenames if you're on Win32. If you're trying this on a non-Windows platform, the mentioned alternative of using /([^\\+])$//([^\\]+)$/ to extract the filename part will still work, with the minor change of using whitespace instead of end of line as the anchor.

Personally, I would approach your log parsing task by splitting on whitespace and then looking closer at the filename part:

my @entries = split "", $record; if ($record[0] eq 'FRAG') { warn "File is $record[8]"; $record[8] =~ /([^\\+])$/ or die "Malformed file entry: '$record[8]'"; warn "Basename is '$1'"; };

Update: Fixed bad typo that rendered the RE useless.


In reply to Re: Regular expression by Corion
in thread Regular expression by PugSA

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.