luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-04-23 23:59:16 +02:00
Code Issues Packages Projects Releases Wiki Activity

Fix a typo

Browse Source 
...and some whitespace fixes. Pointed out by Will Thompson in
bug 602417.
This commit is contained in:
Matthias Clasen 2010-01-02 19:35:08 -05:00
parent 0542e6dbf9
commit 74af99b860
1 changed files with 35 additions and 34 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
gio/gasyncresult.c
View File

@ -53,8 +53,8 @@
* of the operation is not needed, there is no need to call the
* "_finish()" function, GIO will take care of cleaning up the
* result and error information after the #GAsyncReadyCallback
* returns. It is also allowed to take a reference to the #GAsyncResult and
* call "_finish()" later.
* returns. It is also allowed to take a reference to the #GAsyncResult
* and call "_finish()" later.
*
* Example of a typical asynchronous operation flow:
* |[
@ -102,10 +102,11 @@
* always called, even in the case of a cancelled operation. On cancellation
* the result is a %G_IO_ERROR_CANCELLED error.
*
* Some ascynchronous operations are implemented using synchronous calls. These
* are run in a separate thread, if #GThread has been initialized, but otherwise they
* are sent to the Main Event Loop and processed in an idle function. So, if you
* truly need asynchronous operations, make sure to initialize #GThread.
* Some asynchronous operations are implemented using synchronous calls.
* These are run in a separate thread, if #GThread has been initialized, but
* otherwise they are sent to the Main Event Loop and processed in an idle
* function. So, if you truly need asynchronous operations, make sure to
* initialize #GThread.
**/
typedef GAsyncResultIface GAsyncResultInterface;