From 2ec826a984204d034f43a7ad72d835bc99974ede Mon Sep 17 00:00:00 2001 From: Michal Vasko Date: Wed, 17 Oct 2018 13:03:26 +0200 Subject: [PATCH] libyang DOC added note about printers not being thread-safe --- src/libyang.h.in | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/libyang.h.in b/src/libyang.h.in index 4d43f0f44..7351a49ce 100644 --- a/src/libyang.h.in +++ b/src/libyang.h.in @@ -1041,9 +1041,9 @@ extern "C" { * @page howtothreads libyang in Threads * * libyang can be used in multithreaded applications keeping in mind the following rules: - * - libyang context manipulation (adding new schemas) is not thread safe and it is supposed to be done in a main - * thread before any other work with context, schemas or data instances. Destroying the context is supposed to - * be done when no other thread accesses context, schemas nor data trees, + * - libyang context manipulation (adding new schemas, removing schemas or even printing schemas) is not thread safe + * and it is supposed to be done in a main thread before any other work with context, schemas or data instances. + * Destroying the context is supposed to be done when no other thread accesses context, schemas nor data trees, * - data parser (\b lyd_parse*() functions) can be used simultaneously in multiple threads (also the returned * #ly_errno is thread safe), * - data manipulation (lyd_new(), lyd_insert(), lyd_unlink(), lyd_free() and many other