luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-03-15 04:05:11 +01:00
Code Issues Packages Projects Releases Wiki Activity

some wording fixups.

Browse Source 
Fri Mar 24 15:22:04 2006  Tim Janik  <timj@imendio.com>

        * glib/tmpl/atomic_operations.sgml: some wording fixups.
This commit is contained in:
Tim Janik 2006-03-24 14:22:32 +00:00 committed by Tim Janik
parent 601289c545
commit 9e98598d04
2 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/reference/ChangeLog
View File

@ -1,3 +1,7 @@
Fri Mar 24 15:22:04 2006 Tim Janik <timj@imendio.com>
* glib/tmpl/atomic_operations.sgml: some wording fixups.
2006-03-20 Matthias Clasen <mclasen@redhat.com> 2006-03-20 Matthias Clasen <mclasen@redhat.com>
* glib/tmpl/types.sgml: Document G_HAVE_GINT64 as deprecated. * glib/tmpl/types.sgml: Document G_HAVE_GINT64 as deprecated.

8
docs/reference/glib/tmpl/atomic_operations.sgml
View File

@ -22,9 +22,11 @@ counting a very fast operation.
<note> <note>
<para> <para>
You must not directly read integers or pointers concurrently accessed You must not directly read integers or pointers concurrently accessed
by other threads with with the following functions directly. Always use by multiple threads, but use the atomic accessor functions instead.
g_atomic_int_get() and g_atomic_pointer_get() respectively. They are That is, always use g_atomic_int_get() and g_atomic_pointer_get() for
acting as a memory barrier. read outs.
They provide the neccessary synchonization mechanisms like memory
barriers to access memory locations concurrently.
</para> </para>
</note> </note>