Re: line execution order changes by machine/env

Just a guess... people are sometimes confused about warnings showing immediately (STDERR) while print statements are buffered (STDOUT).

This can give the impression of differing execution order.

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)

Je suis Charlie!}

Comment on Re: line execution order changes by machine/env

Replies are listed 'Best First'.
Re^2: line execution order changes by machine/env by davefg (Initiate) on Jun 12, 2017 at 19:12 UTC
Sorry for the vagary. I don't have specifics. But yes, lines of code, not line of data from a file. I haven't seen the code (yet). I don't think it'll be due to iterating through a hash. He's too good not to consider that. The STDERR vs STDOUT sound like a real possibility, one that I'll keep in mind. I saw something like this years ago when working with Perl/Tk. Correct if wrong, but that would be multi-threaded, interrupt driven thing where synching may not be as simple as observing what lines of code come before others. Good ideas, thanks for the input. Will add to this if/when I get code. Reducing the script down to the bare bones that still demos the behavior is a good idea. Done that sort of thing before, good strategy.	[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.