On Sat, 13 Aug 2005, Veli-Pekka Tätilä wrote:
> Ok, good to know and thanks for a quick reply. Is this fact already
> mentioned in the docs? I must confess I haven't looked at the OLE docs
No, it is not really mentioned in the docs, just in the TODO file of
the source distribution.
> too closely, I've learned most of what I've needed to know from OLE in
> the Gecko book and Visual Studio 6 OLE Viewer. The Gecko book says
> that Active State distroes should use OLE rather than Win32::OLE. Is
> this up to date info and will the OLE module work differently in terms
> of threading?
No, the Gecko book is very much out of date. You should always use
Win32::OLE instead of just OLE in any new code. The OLE module is
just a compatibility wrapper on top of Win32::OLE for code that
has been written for Perl 5.003_07 ("Perl for Win32").
> I reckon the problem lies with PErl in the end. Oddly enough I can
> use multi-threaded OLE servers somewhat. For instance speaking
> text through SAPI 5 asynchronously provided that I sleep some ms
> in Perl so that the SAPI thread has CPU time to speak up. If I try
> to do something heavy while the SAPI 5 thread is speaking, it
> seems to be starving mostly. I haven't experienced the same
> problem in C++ and Win32.
Calling multithreaded COM components from Win32::OLE is a completely
different topic from using Win32::OLE in a multithreaded Perl program.
The former should be supported, but the latter isn't.
Cheers,
-Jan
_______________________________________________
Perl-Win32-Users mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
