Others have commented on your code. I just wanted to mention something about the comments in your code.

It's much better to make a block comment before a section to describe what the section is doing, and leave out all the single-line comments that are obvious from the code. For instance, "#Path to perl interpreter" and "#Open the file links.txt for appending" are obvious from the code and should be eliminated. They only clutter up the code itself, and make it more difficult to follow the flow of the program.

The Practice of Programming by Kernigan & Pike has a chapter that goes over basic coding style, and is an excellent guide for good commenting.

In reply to Re: Pretty cool link extractor. by jeffenstein
in thread Pretty cool link extractor. by DigitalKitty

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.