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

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!
  • Comment on Re^4: Win32::OLE and fork causes null pointer exception

Replies are listed 'Best First'.
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.
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.