Expandplf_updates.txt:-
/****************************ORPHANED FILES***************************
+/
  //source/modem/hdr/cp/rel/07.01.00.13.20/inc/hdr.c#2 
 //source/modem/hdr/cp/rel/07.01.00.13.20/inc/hdrscmgmmcdp.h#2 
/*************************** FILES IN VU's***************************/
 /******************************* PLF's******************************/
 
my $expand_line = <Expandplf_updates.txt>;
open my $FH, '<', "$expand_line" or die "could not open $expand_plf - 
+$!"; 
while (<$FH>) {
    chomp;
        print "IN\n";
    next unless ( m:(\/\/.+?)#(\d+)$: );//why is the above input not m
+atching this line.

    print "\nMATCH DATA:$1 $2";//doesnt print this

[download]

In reply to Regex not matching by perl_mystery

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.