CondDestroy
Destroys a multi-threading conditional variable when it is no more needed
CondDestroy ( handle )
handle
Once the conditional is CondCreated and the threads are started, one of more of them (including the main thread executing main program) can be set to CondWait for the conditional, they will be stopped until some other thread CondSignals that the waiting thread can restart. CondBroadcast can be used to restart all threads waiting for the conditional. At the end of the program CondDestroy must be used to avoid leaking resources in the OS.
Conddestroy destroys a condition variable, freeing the resources it might hold. No threads must be waiting on the condition variable on entrance to Conddestroy.
Syntax
Usage
CondDestroy ( handle )
Parameters
handle
The handle of a conditional variable to destroy.
Description
Once the conditional is CondCreated and the threads are started, one of more of them (including the main thread executing main program) can be set to CondWait for the conditional, they will be stopped until some other thread CondSignals that the waiting thread can restart. CondBroadcast can be used to restart all threads waiting for the conditional. At the end of the program CondDestroy must be used to avoid leaking resources in the OS.
Conddestroy destroys a condition variable, freeing the resources it might hold. No threads must be waiting on the condition variable on entrance to Conddestroy.
Example
Platform Differences
- Conddestroy is not available with the DOS version / target of FreeBASIC, because multithreading is not supported by DOS kernel nor the used extender.
Dialect Differences
- Threading is not allowed in -lang qb
Differences from QB
- New to FreeBASIC
See also