part of the problem is that $SecOff is somehow undefined, at least when I run it through the debugger.

That's not what it looks like to me. Instead, it would appear to me that @_ somehow is empty, or partly empty, or filled with a few undefined values. At least, the number of warnings and the line number they occur at, would agree with it: pack with empty $_[4] and $_[5] (line 67), addition with empty $_[3] (line 68), $_[5] (line 69), and $_[3] (line 67).

I do not see what could cause that, though. It's an odd error — perhaps even a Perl bug for version 5.8.6. It's the last line in the sub _timegm I currently have under suspicion: 

    $sec +  86400 * &_daygm;

[download]
Can anybody confirm @_ is passed unaltered, on 5.8.6, when a sub is called with "&" and without parens?

In reply to Re: Lots of errors from Time::Local on Windows by bart
in thread Lots of errors from Time::Local on Windows by sgifford

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.