Hi: My boss hinted that he might have me look at a problem he's having running a perl script. Wanting to be proactive in finding a solution, I'm posing the problem to the community for initial feedback. He claims that perl executes lines in the expected order on one machine, but executes them in a different order on a different machine (both linux, same version of perl, machine configs the same (or so he says)). What could account for behavior like this? I've seen something like this myself in the past but never figured it out. Back then (if memory serves) it would run fine in the debugger, but the order of execution would be different outside the debugger. Just looking for possible explanations and, if possible, solutions. Thanks in advance. And sorry for the lack of details.

In reply to line execution order changes by machine/env by davefg

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.