Jan Dubois wrote: >On Tue, 21 Sep 2004, Steve Hay wrote: > > >>(Non-Win32 users: The real issue here is not Win32-specific.) >> >> > >As to Win32::Shortcut: you should just delete the END block from the module. >I see that Sarathy already did this over a year for the version that ships >with ActivePerl. He also gave me his mailbox with accumulated libwin32 >patches and asked me to put out another libwin32 release to CPAN. >Unfortunately I haven't found time to get around to it yet. > Oh - I looked on CPAN for a newer libwin32 or Win32::Shortcut (and even tried dada.perl.it), but didn't think of looking in the latest ActivePerl!
I'm a little wary of this fix because MSDN docs say "An apartment must call CoUninitialize once for each successful call it has made to CoInitialize" and "CoUninitialize should be called on application shutdown", but it certainly seems to work and is less messy than what I was doing. > >The other issue you are seeing is that CoInitialize() needs to be called >in each *thread* that wants to make COM calls. To do this properly, the >module needs to provide a CLONE method if you are using Perl threads in >5.8.x. > That's not an issue for me with mp1 because it's single-threaded on Win32. I'll have to bear it in mind when moving to mp2, though, 'cos that's multi-threaded on Win32. > >I have no clue how all this relates to MP1; it is just the subject line that >made me take a brief peek at this message. > Thanks for the tip. It's interesting to note that the purveyors of PerlEx watch this list :) ... - Steve ------------------------------------------------ Radan Computational Ltd. The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email. -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
