From 0ba05ca500ecb1269b3ba67761e1329e0934f40c Mon Sep 17 00:00:00 2001 From: Marc Mutz Date: Fri, 6 Jun 2025 16:59:43 +0200 Subject: [PATCH] [docs] IPC: don't mention undoc'ed QBasicAtomic Use Q(non-Basic)Atomic instead. Amends 7a370838177e581c8a9342808ba86e081951a41c. Task-number: QTBUG-55421 Pick-to: 6.10 6.9 6.8 Change-Id: Ia8cc059a94acbee667c19b443ed2e2f487b56806 Reviewed-by: Thiago Macieira --- src/corelib/doc/src/ipc.qdoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/corelib/doc/src/ipc.qdoc b/src/corelib/doc/src/ipc.qdoc index 7ec6f5fa3b4..779254b8437 100644 --- a/src/corelib/doc/src/ipc.qdoc +++ b/src/corelib/doc/src/ipc.qdoc @@ -139,7 +139,7 @@ To achieve locking of the shared memory segment, applications will need to deploy their own mechanisms. One way may be to use \l QLockFile. Another - and less costly solution is to use QBasicAtomicInteger or \c{std::atomic} in + and less costly solution is to use QAtomicInteger or \c{std::atomic} in a pre-determined offset in the segment itself. Higher-level locking primitives may be available on some operating systems; for example, on Linux, applications can set the "pshared" flag in the mutex attribute