This is possibly the ugliest code I have ever seen. The comments essentially obfuscate the code and the indentation is semi-random. I suggest you get a copy of Perltidy and run the code through it with the -dbc option to delete the comments and fix the indentation, that way you can actually see the code and control logic. As it stands it is essentially unreadable and unmaintainable.

If you search for the error message "Can't open the file" you will find the if(@did_not_save) that triggers it. Go and find where @did_not_save is set and you will see the logic that makes this happen. Observe that the error message filename and the name of the file being opened are different, fix that, get a useful error message......

In reply to Re: Working With Sub-Par Code by tachyon-II
in thread Working With Sub-Par Code by stonecolddevin

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.