fix ToxAV threading documentation

ToxAV is not thread-safe at the moment, remove that claim from the
header file.
This commit is contained in:
sudden6 2019-11-14 13:11:13 +01:00
parent 1b7d7b66c5
commit 683bc802e2
No known key found for this signature in database
GPG Key ID: 279509B499E032B9
2 changed files with 4 additions and 4 deletions

View File

@ -53,8 +53,8 @@ extern "C" {
/** \subsection threading Threading implications /** \subsection threading Threading implications
* *
* Unlike the Core API, this API is fully thread-safe. The library will ensure * Only ${toxAV.iterate} is thread-safe, all other functions must run from the
* the proper synchronization of parallel calls. * tox thread.
* *
* A common way to run ToxAV (multiple or single instance) is to have a thread, * A common way to run ToxAV (multiple or single instance) is to have a thread,
* separate from tox instance thread, running a simple ${toxAV.iterate} loop, * separate from tox instance thread, running a simple ${toxAV.iterate} loop,

View File

@ -49,8 +49,8 @@ extern "C" {
*/ */
/** \subsection threading Threading implications /** \subsection threading Threading implications
* *
* Unlike the Core API, this API is fully thread-safe. The library will ensure * Only toxav_iterate is thread-safe, all other functions must run from the
* the proper synchronization of parallel calls. * tox thread.
* *
* A common way to run ToxAV (multiple or single instance) is to have a thread, * A common way to run ToxAV (multiple or single instance) is to have a thread,
* separate from tox instance thread, running a simple toxav_iterate loop, * separate from tox instance thread, running a simple toxav_iterate loop,