in reply to Lite.pm Causing Problems
No, nor will applying undef to your globals fix the problem. The problem is that, somewhere in your code, a Win32::OLE object handle is getting corrupted, and the destructor in Win32::OLE::Lite is finding that a resource it is supposed to release is not there and complaining about this state of affairs.
That the warning is getting into your data means that you should consider explicitly writing your data to a file instead of redirecting the script's output. You will still get this warning until you fix the underlying problem, but it will no longer be mixed into your data.
A SSCCE would also be very helpful, as the lack of information in your question required me to make some guesses in the above answer.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Lite.pm Causing Problems
by Anonymous Monk on Sep 06, 2019 at 02:57 UTC | |
by jcb (Parson) on Sep 06, 2019 at 04:05 UTC | |
by Anonymous Monk on Sep 06, 2019 at 04:20 UTC | |
by jcb (Parson) on Sep 06, 2019 at 04:27 UTC | |
|