Re: Why can't some of my modules do log output to a file?

In addition to kcott's reference here to advice about asking effective questions, consider constructing a Short, Self-Contained, Correct Example. Just the process of constructing an SSCCE may give you enough insight to solve the problem, and if it doesn't, at least you'll have an example to clearly demonstrate the problem to others. But try to keep it short.

Give a man a fish: <%-{-{-{-<

Comment on Re: Why can't some of my modules do log output to a file? Download Code

Replies are listed 'Best First'.
Re^2: Why can't some of my modules do log output to a file? by LittleJack (Beadle) on Oct 12, 2022 at 01:13 UTC
I thought I had provided a short, self-contained, correct example? I can't really provide a seventeen-layered SSCCE of Foo.pm calling Bar.pm calling Baz.pm calling Bax.pm etc. etc. where it's turtles all the way down.	[reply]
Re^3: Why can't some of my modules do log output to a file? by AnomalousMonk (Archbishop) on Oct 12, 2022 at 04:03 UTC
I thought I had provided a short, self-contained, correct example? The only code that I can see that you've provided so far in the thread is the code in the OP. This code is not self-contained and executable (under strict-ures and warnings). If it were made so, I very much doubt it would manifest any error/warning messages at all. Please see the SSCCE discussion. I can't really provide a seventeen-layered SSCCE ... But apparently the monks are expected to do so. Give a man a fish: `<%-{-{-{-<`	[reply] [d/l]
Re^3: Why can't some of my modules do log output to a file? by haukex (Archbishop) on Oct 12, 2022 at 05:43 UTC
I thought I had provided a short, self-contained, correct example? An SSCCE should be runnable on its own, and it must reproduce the problem. Especially the latter is a very important debugging step: removing as much code as possible while still keeping the problem present will help you focus on the source of the problem.	[reply]