File: pr_notifycondvar.rst

package info (click to toggle)
thunderbird 1%3A115.16.0esr-1~deb12u1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 3,476,252 kB
  • sloc: cpp: 6,972,150; javascript: 5,209,211; ansic: 3,507,222; python: 1,137,609; asm: 432,531; xml: 205,149; java: 175,761; sh: 116,485; makefile: 22,152; perl: 13,971; objc: 12,561; yacc: 4,583; pascal: 2,840; lex: 1,720; ruby: 1,075; exp: 762; sql: 666; awk: 580; php: 436; lisp: 430; sed: 70; csh: 10
file content (49 lines) | stat: -rw-r--r-- 1,211 bytes parent folder | download | duplicates (18)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
PR_NotifyCondVar
================

Notifies a condition variable of a change in its associated monitored
data.


Syntax
------

.. code::

   #include <prcvar.h>

   PRStatus PR_NotifyCondVar(PRCondVar *cvar);


Parameter
~~~~~~~~~

:ref:`PR_NotifyCondVar` has one parameter:

``cvar``
   The condition variable to notify.


Returns
~~~~~~~

The function returns one of the following values:

-  If successful, ``PR_SUCCESS``.
-  If unsuccessful (for example, if the caller has not locked the lock
   associated with the condition variable), ``PR_FAILURE``.


Description
-----------

The calling thread must hold the lock that protects the condition, as
well as the invariants that are tightly bound to the condition.

Notification of a condition variable signals a change of state in some
monitored data. When the notification occurs, the runtime promotes a
thread that is waiting on the condition variable to a ready state. If
more than one thread is waiting, the selection of which thread gets
promoted cannot be predicted. This implies that all threads waiting on a
single condition variable must have the same semantics. If no thread is
waiting on the condition variable, the notify operation is a no-op.