One issue that you should be aware of is that when opening a filehandle, you must use or die: $!. Also, if $basepath and $basename are different variables, there is some wierd stuff that goes on. I guess what is happening in that snippet is that Perl is being confused by you using 2 variables in that syntax and instance of using open. I walked over to another machine and threw together a little sumpthin' sumpthin' and the only thing that worked for me is catenating $basepath and $basename. So, 

open HTML, ">$basepath/$basename.html";

[download]

Should be: 

$foo = "$basepath"."$basename.html";

open HTML, ">foo" or die "Can't open $foo: $!";

[download]

Also make sure that if $basename is a HTML file, that the *value* of the variable has a suffix of '.html'.

redmist
redmist@users.sourceforge.net

In reply to Re: open() destroying my vars? by redmist
in thread open() destroying my vars? by theorbtwo

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.