From 683bc802e28934045d210ecb14609bde32de5d82 Mon Sep 17 00:00:00 2001 From: sudden6 Date: Thu, 14 Nov 2019 13:11:13 +0100 Subject: [PATCH] fix ToxAV threading documentation ToxAV is not thread-safe at the moment, remove that claim from the header file. --- toxav/toxav.api.h | 4 ++-- toxav/toxav.h | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/toxav/toxav.api.h b/toxav/toxav.api.h index 46e4b226..5d8a8b26 100644 --- a/toxav/toxav.api.h +++ b/toxav/toxav.api.h @@ -53,8 +53,8 @@ extern "C" { /** \subsection threading Threading implications * - * Unlike the Core API, this API is fully thread-safe. The library will ensure - * the proper synchronization of parallel calls. + * Only ${toxAV.iterate} is thread-safe, all other functions must run from the + * tox 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, diff --git a/toxav/toxav.h b/toxav/toxav.h index bfb7617c..daa1314d 100644 --- a/toxav/toxav.h +++ b/toxav/toxav.h @@ -49,8 +49,8 @@ extern "C" { */ /** \subsection threading Threading implications * - * Unlike the Core API, this API is fully thread-safe. The library will ensure - * the proper synchronization of parallel calls. + * Only toxav_iterate is thread-safe, all other functions must run from the + * tox 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,