Re^3: Win32::OLE and fork causes null pointer exception

in reply to Re^2: Win32::OLE and fork causes null pointer exception
in thread Win32::OLE and fork causes null pointer exception

Try require rather than use, either:

in the new Thread, or
in the main thread below the call to threads->new.

If it doesn't work at all (once we've tried all the standard work-arounds), I'd say you could call it a bug in Win32::OLE.

-David

Comment on Re^3: Win32::OLE and fork causes null pointer exception Select or Download Code

Replies are listed 'Best First'.
Re^4: Win32::OLE and fork causes null pointer exception by jrsimmon (Hermit) on Nov 15, 2007 at 16:34 UTC
This looks promising...the test script at least runs now with a combination of import and require in the thread subroutine. Thanks for your help!	[reply]
Re^5: Win32::OLE and fork causes null pointer exception by jrsimmon (Hermit) on Nov 15, 2007 at 16:45 UTC
For the record, using require and import appears to work with fork as well as with Threads.	[reply]
Re^5: Win32::OLE and fork causes null pointer exception by jrsimmon (Hermit) on Nov 27, 2007 at 23:18 UTC
Just a follow-up...unfortunately Win32::OLE will not work in any multi-threaded application. I dug around and found a forum with a post by the author indicating this was a known limitation that may be addressed in the future, but would require a significant amount of work. For my current needs, I split the one script into two separate scripts.	[reply]

In Section Seekers of Perl Wisdom