SRFI-18 does not specify a “wait” function for condition variables.
Waiting on a condition variable can be simulated using the SRFI-18
mutex-unlock! function described in the previous section, or
Guile's built-in wait-condition-variable procedure can be used.
Returns
#tif obj is a condition variable,#fotherwise. This is the same procedure as the same-named built-in procedure (seecondition-variable?).
Returns a new condition variable, optionally assigning it the object name name, which may be any Scheme object. This procedure replaces a procedure of the same name in the core library.
Returns the name assigned to thread at the time of its creation, or
#fif it was not given a name.
Get or set the “object-specific” property of condition-variable. In Guile's implementation of SRFI-18, this value is stored as an object property, and will be
#fif not set.
Wake up one thread that is waiting for condition-variable, in the case of
condition-variable-signal!, or all threads waiting for it, in the case ofcondition-variable-broadcast!. The behavior of these procedures is equivalent to that of the proceduressignal-condition-variableandbroadcast-condition-variablein the core library.