]> git.saurik.com Git - wxWidgets.git/blame - docs/doxygen/groups/funcmacro_atomic.h
Resolve ambiguity between GetClientXXX() methods in wxOSX wxComboBox.
[wxWidgets.git] / docs / doxygen / groups / funcmacro_atomic.h
CommitLineData
dae2800a
BP
1/////////////////////////////////////////////////////////////////////////////
2// Name: funcmacro_atomic.h
3// Purpose: Atomic Operation function and macro group docs
4// Author: wxWidgets team
5// RCS-ID: $Id: funcmacro_gdi.h 52454 2008-03-12 19:08:48Z BP $
526954c5 6// Licence: wxWindows licence
dae2800a
BP
7/////////////////////////////////////////////////////////////////////////////
8
9/**
10
11@defgroup group_funcmacro_atomic Atomic Operations
12@ingroup group_funcmacro
13
14When using multi-threaded applications, it is often required to access or
15modify memory which is shared between threads. Atomic integer and pointer
16operations are an efficient way to handle this issue (another, less efficient,
1ba0de2e
BP
17way is to use a wxMutex or wxCriticalSection). A native implementation exists
18for Windows, Linux, Solaris and Mac OS X; for others, a wxCriticalSection is
19used to protect the data.
dae2800a 20
1ba0de2e
BP
21One particular application is reference counting (used by so-called
22@ref group_class_smartpointers "smart pointers").
dae2800a
BP
23
24You should define your variable with the type wxAtomicInt in order to apply
25atomic operations to it.
26
dae2800a
BP
27*/
28