apr-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 40971] New: - apr_thread_cond_signal insufficiently documented
Date Tue, 14 Nov 2006 14:48:29 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40971>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40971

           Summary: apr_thread_cond_signal insufficiently documented
           Product: APR
           Version: HEAD
          Platform: All
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: APR
        AssignedTo: bugs@apr.apache.org
        ReportedBy: eddie_epstein@aewatercolors.com


The behavior of this method is quite different on Unix vs win32 platforms. A
minor change to one header file would help quite a bit. 
Suggested patch follows.

--- apr_thread_cond.h.~1~	2006-11-14 09:22:44.669864500 -0500
+++ apr_thread_cond.h	2006-11-14 09:36:46.805317900 -0500
@@ -95,9 +95,11 @@
                                                     apr_interval_time_t timeout);
 
 /**
- * Signals a single thread, if one exists, that is blocking on the given
- * condition variable. That thread is then scheduled to wake up and acquire
- * the associated mutex. Although it is not required, if predictable scheduling
+ * Signals a single thread that is blocking on the given condition variable.
+ * That thread is then scheduled to wake up and acquire the associated mutex.
+ * Effect if no thread is currently waiting: on Unix, nothing; on win32,
+ * will immediately wake up the next thread to block on the given condition.
+ * Although it is not required, if predictable scheduling
  * is desired, that mutex must be locked while calling this function.
  * @param cond the condition variable on which to produce the signal.
  */

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Mime
View raw message