Well, your regex isn't enough, because while it matches /*, it doesn't check whether that occurs inside a string or not - and when it's inside a string, it's not the start of the comment. I won't repeat the regex here, you can find it in the hip owls book, and there are pointers to it already posted.

As for your second question, it's not just the first line that's echoed, it's the second line too, there's a /* after the MATCH! The reason is your use of -p, which means that $_ is printed for each line of input processed. Regardless of any print statements in the program. You probably want to use -n instead.

-- Abigail

In reply to Re: Matching C-Style comments by Abigail
in thread Matching C-Style comments by Anonymous Monk

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.