Hi Andrew,
During a forum discussion i got the following information from the
author of twapi:
https://sourceforge.net/forum/message.php?msg_id=4193122
<quote>
The issue is that the low level Win32<->Tcl bindings source code is
generated using SWIG (see swig.org). The generated code is not in
theory thread-safe (no locks around global structures etc.). I can't
really fix this easily because I would have to go and change the SWIG
code generator itself.
At the same time, as far as I can tell the global structures are
initialized and not modified thereafter. Furthermore, initialization
is protected by a boolean (albeit without locked access). So there is
a good chance it will "mostly" work but I can't really guarantee it.
</quote>
What's your opinion on this?
Also i'm now thinking about creating some test cases and trying it out.
kind regards,
Jamshed
On 7 Mar 2007, at 23:49, Andrew Piskorski wrote:
If you need the twapi functionality from AOLserver, I'd just try it.
If twapi's author believes that twapi is written in a mostly
thread-safe manner (e.g., no global variables), but he's just never
tested it in multi-threaded use, then it seems a reasonable bet that
any thread-safety problems you encounter won't be that bad to fix.
(I've no idea how much of twapi is Tcl and how much is Windows C code,
though. C is of course more work to fix than Tcl.)
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
