No, it produces the same results in the debugger as on the command line. It's just that the debugger doesn't show any unexpected or unusual conditions. All the variables are what they should be. All the return codes are good and so on. The print statement just doesn't seem to work. Actually I suspect disk buffering in some way since it works to STDOUT although I have no idea what the problem might be.
in reply to Re^3: Odd behaviour from print statement
in thread Odd behaviour from print statement
use strict; use warnings; use diagnostics;