he producer says)
>>>>>>> can't work in multithread environment.
>>>>>>> As each connection thread needs to call functions of this third
___
Bug-commoncpp mailing list
Bug-commoncpp@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-commoncpp
__ NOD32 2011 (20070127) Information __
This message was checked by NOD32
otected function call (a function that can't work
>>>>> in multithread env) <---
>>>>> mutex.leaveMutex();
>>>>>}
>>>>> }
>>>>> ...
>>>>> in 99% of cases it works fine. But i
ttp://lists.gnu.org/mailman/listinfo/bug-commoncpp
__ NOD32 2011 (20070127) Information __
This message was checked by NOD32 antivirus system.
http://www.eset.com
__ NOD32 2014 (20070128) Information __
This message was checked by NOD32 antivir
Thanks for your reply.
Can you write an example with the semaphore in this context?
Thanks,
Carlo
David Sugar ha scritto:
I think what he really wants to do is use the Common C++ Semaphore with
a count of 1, since semaphore can block with a "timeout", and with a "1"
count in effect acts as
This seemed like a good time to discuss some current ideas for common
c++ 2.0...
First, I have wanted to make object management smarter, and borrow a
little from objective-c. Hence, we will have a new commonly used
virtual base class, "Object", which will include a release() virtual.
This can be
