[glibmm/glibmm-2-54] AsyncResult: Bin obsolete docs re: initing GThread
- From: Daniel Boles <dboles src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [glibmm/glibmm-2-54] AsyncResult: Bin obsolete docs re: initing GThread
- Date: Sun, 20 May 2018 15:39:11 +0000 (UTC)
commit 7d8b778aae95e8cf425ea040fa370caf3c6b9ebb
Author: Daniel Boles <dboles src gnome org>
Date: Sun May 20 16:16:05 2018 +0100
AsyncResult: Bin obsolete docs re: initing GThread
As the GLib Threads documentation states:
“Since version 2.32, the GLib threading system is automatically
initialized at the start of your program, and all thread-creation
functions and synchronization primitives are available right away.”
gio/src/asyncresult.hg | 3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
---
diff --git a/gio/src/asyncresult.hg b/gio/src/asyncresult.hg
index 10a80c6..7795deb 100644
--- a/gio/src/asyncresult.hg
+++ b/gio/src/asyncresult.hg
@@ -94,9 +94,6 @@ using SlotAsyncReady = sigc::slot<void, Glib::RefPtr<AsyncResult>&>;
* The callback for an asynchronous operation is called only once, and is always called, even in the case of
a cancelled operation.
* On cancellation the result is a ERROR_CANCELLED error.
*
- * Some ascynchronous operations are implemented using synchronous calls. These are run in a separate
GThread, 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.
- *
* @newin{2,16}
*/
class AsyncResult : public Glib::Interface
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]