I always find repeated "print OUT" a bit clunky. Two alternatives: 
$outputFile = "fulltoc.htm";
open(OUT, ">",$outputFile) or die "couldn't open outputfile: $!";
select OUT;
print ("<HTML><HEAD><TITLE>");
print ("Detailed Table of Contents\n");
print ("</TITLE></HEAD><BODY>\n");

[download]

Or: 

$outputFile = "fulltoc.htm";
open(OUT, ">",$outputFile) or die "couldn't open outputfile: $!";
print OUT "<HTML><HEAD><TITLE>"
        . "Detailed Table of Contents\n"
        . "</TITLE></HEAD><BODY>\n";

[download]

Note that with the first approach, you'd have to explicitly print to STDOUT when you want to print to the screen: 

print STDOUT "$file\n";

[download]

I was also surprised by this line: 

next if $file =~ m/^\.htm$/i;   
next unless $file =~ m/\.htm$/i;  # not this?

[download]

In reply to Re: unable to open input file by hbm
in thread unable to open input file by grashoper

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.