Re^3: END{} Subroutine not being called for Child process

In general I don't redirect STDOUT or STDERR to /dev/null and never when I am debugging. Very often, when something unexpected goes wrong, important clues are written to one of these outputs. This may include output from modules that have been used, which might not be obvious without reading all the module source.

Comment on Re^3: END{} Subroutine not being called for Child process

Replies are listed 'Best First'.
Re^4: END{} Subroutine not being called for Child process by SituationSoap (Acolyte) on Aug 05, 2009 at 12:51 UTC
Point well taken. I can see the benefits of not redirecting those outputs, especially during a debugging process. From a long term solution, I think this is the right answer for the script as written, however. If I were to rewrite it, I might rewrite it to simply open those outputs to files instead, but the handling code is already written (and readable, and functional), so I don't see a lot of value in re-factoring that part of the code right now.	[reply]

Replies are listed 'Best First'.

Re^4: END{} Subroutine not being called for Child process
by SituationSoap (Acolyte) on Aug 05, 2009 at 12:51 UTC

Point well taken. I can see the benefits of not redirecting those outputs, especially during a debugging process. From a long term solution, I think this is the right answer for the script as written, however. If I were to rewrite it, I might rewrite it to simply open those outputs to files instead, but the handling code is already written (and readable, and functional), so I don't see a lot of value in re-factoring that part of the code right now.

[reply]