To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=44627
------- Additional comments from [EMAIL PROTECTED] Thu Mar 10 07:15:12 -0800
2005 -------
[EMAIL PROTECTED]: You're right about the Win32 API. SetEvent wakes up all
waiting
threads regardless of a subsequent ResetEvent call. PulseEvent f.e. does an
automatic reset. Events can also created with the automatic flags what results
in
SetEvent will behave like PulseEvent.
It's not the question what might be the right way to implement this. The
platform
implementations have to be consistent.
OSL documentation says:
/** Sets condition to True => wait() will not block, check() returns True.
NOTE: ALL threads waiting on this condition are unblocked!
@param Condition handle to a created condition.
@return False if system-call failed.
*/
For me that means it behaves like the Win32 SetEvent and we should not change
the semantics just for being so "cool" to act like the pthread library. The
only right
way to implement osl_setCondition is to behave like documented.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
